Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix multiple open issues #927

Merged
merged 11 commits into from
Mar 9, 2015
Merged

Fix multiple open issues #927

merged 11 commits into from
Mar 9, 2015

Conversation

mgreter
Copy link
Contributor

@mgreter mgreter commented Mar 8, 2015

Addresses/Fixes #317 and #871

Added a lot of other small fixes ("low hanging fruits")!

@mgreter mgreter force-pushed the bugfix/issue_317 branch 2 times, most recently from e3c15dc to f624df0 Compare March 8, 2015 05:31
Prints the exact error message as ruby sass.
Prints the exact error message as ruby sass.
Implements optional flag to suppress message.
Evaluate the actual queries against each other.
We probably need to implement a better test here!
@mgreter mgreter self-assigned this Mar 9, 2015
@mgreter mgreter added this to the 3.2 milestone Mar 9, 2015
@mgreter mgreter changed the title [WIP] Fix behavior with invalid extends Fix behavior with invalid extends Mar 9, 2015
@mgreter mgreter changed the title Fix behavior with invalid extends Fix multiple open issues Mar 9, 2015
Fixes sass#879
Should work for all prepended texts (like top-comments)
@xzyfer
Copy link
Contributor

xzyfer commented Mar 9, 2015

It's worth breaking this up into multiple PRs. Having PRs that fix multiple issues is messy IMHO and it means all these fixes can't be merged because of a single failing commit. This is also makes it difficult for me to figure out what I should be working without accidentally re-doing work you've done.

@mgreter
Copy link
Contributor Author

mgreter commented Mar 9, 2015

@xzyfer I know it's a bit messy, but it's easier this way to have a linear commit history. I can create single PRs for each issue. But it adds quite a lot of additional work, that is basically not giving any value to the final code base! So I hope we can merge this "en gros". I also assigned myself to all issues that are covered by this PR, so you should be able to get a list of issues I'm working on/have fixed!

@mgreter
Copy link
Contributor Author

mgreter commented Mar 9, 2015

My spec-runner tells me that the following test will now pass:

  • todo-issues/issue_346
  • todo-issues/issue_535
  • todo-tests/scss-tests/126_test_media_interpolation_with_reparse

Most other fixes address issues that are either missing spec tests, source map related or about error reporting, which is not yet tested by the sassc spec runner (I have some tests in perl-libsass)!

@mgreter mgreter mentioned this pull request Mar 9, 2015
@xzyfer
Copy link
Contributor

xzyfer commented Mar 9, 2015

Yeah sure, it's just worth keeping in mind in the future. Since we're in different timezones we're likely to step on each others toes. It's worth just merge PR with small discrete chucks rather than large multi-purpose PRs IMHO.

Nice work on this!

@xzyfer
Copy link
Contributor

xzyfer commented Mar 9, 2015

After this is merged I'll update sass/sass-spec#271 with those specs.

@mgreter
Copy link
Contributor Author

mgreter commented Mar 9, 2015

OK, I'm merging this then! The code in this PR is probably not always the cleanest, but we need to get things going in a direction, so better than failing spec tests IMO. And there is a lot of existing code that could need improvement, and I basically just trust the spect tests and CI here 🚀

mgreter added a commit that referenced this pull request Mar 9, 2015
@mgreter mgreter merged commit 51ffdcd into sass:master Mar 9, 2015
@xzyfer
Copy link
Contributor

xzyfer commented Mar 9, 2015

Agreed.

@mgreter mgreter deleted the bugfix/issue_317 branch March 10, 2015 00:05
@mgreter mgreter restored the bugfix/issue_317 branch March 10, 2015 00:05
@drewwells
Copy link
Contributor

FYI: I'm getting runtime exceptions with these changes

@mgreter
Copy link
Contributor Author

mgreter commented Mar 10, 2015

@drewwells can you tell which commit introduces your problems?
There was a breaking change in #925 for implenters!

@drewwells
Copy link
Contributor

5757248 works fine, but this merge broke
it. I can try bisecting the merge for which commit introduced it.

On Mon, Mar 9, 2015 at 7:22 PM Marcel Greter notifications@github.com
wrote:

@drewwells https://github.com/drewwells can you tell which commit
introduces your problems?


Reply to this email directly or view it on GitHub
#927 (comment).

@mgreter
Copy link
Contributor Author

mgreter commented Mar 10, 2015

Would be helpfull to have a specific commit to pin your issue!

@drewwells
Copy link
Contributor

I wasn't sure how to bisect a merge, but appears you can!
b5235ec
introduced the exception.

On Mon, Mar 9, 2015 at 7:30 PM Marcel Greter notifications@github.com
wrote:

Would be helpfull to have a specific commit to pin your issue!


Reply to this email directly or view it on GitHub
#927 (comment).

@drewwells
Copy link
Contributor

Sorry, I'm not easily reproducing the problem. I'll keep digging and file an issue if I can find the problem. After cleaning and rebuilding several times on latest master, I'm not reproducing this. Maybe it was just a build problem.

@mgreter
Copy link
Contributor Author

mgreter commented Mar 10, 2015

Yep, you need to make clean if some header structures have changed, which was definitely the case!

@drewwells
Copy link
Contributor

That's probably it, thanks for the info.

On Tue, Mar 10, 2015 at 2:38 AM Marcel Greter notifications@github.com
wrote:

Yep, you need to make clean if some header structures have changed, which
was definitely the case!


Reply to this email directly or view it on GitHub
#927 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment