-
Notifications
You must be signed in to change notification settings - Fork 463
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
Conversation
e3c15dc
to
f624df0
Compare
Prints the exact error message as ruby sass.
Prints the exact error message as ruby sass. Implements optional flag to suppress message.
bb78292
to
6294ec3
Compare
Evaluate the actual queries against each other. We probably need to implement a better test here!
6294ec3
to
f65aa5f
Compare
Adds block stack for parser to do this check! Fixes sass#325
6f360d2
to
ba1750e
Compare
ba1750e
to
5606d26
Compare
22827bb
to
ff1b08d
Compare
Fixes sass#879 Should work for all prepended texts (like top-comments)
ff1b08d
to
21ce837
Compare
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. |
@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! |
My spec-runner tells me that the following test will now pass:
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)! |
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! |
After this is merged I'll update sass/sass-spec#271 with those specs. |
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 🚀 |
Agreed. |
FYI: I'm getting runtime exceptions with these changes |
@drewwells can you tell which commit introduces your problems? |
5757248 works fine, but this merge broke On Mon, Mar 9, 2015 at 7:22 PM Marcel Greter notifications@github.com
|
Would be helpfull to have a specific commit to pin your issue! |
I wasn't sure how to bisect a merge, but appears you can! On Mon, Mar 9, 2015 at 7:30 PM Marcel Greter notifications@github.com
|
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. |
Yep, you need to make clean if some header structures have changed, which was definitely the case! |
That's probably it, thanks for the info. On Tue, Mar 10, 2015 at 2:38 AM Marcel Greter notifications@github.com
|
Addresses/Fixes #317 and
#871Added a lot of other small fixes ("low hanging fruits")!