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

Any plans to add trace_selectors support? #1222

Closed
Tracked by #1892
drone1 opened this issue May 17, 2015 · 9 comments
Closed
Tracked by #1892

Any plans to add trace_selectors support? #1222

drone1 opened this issue May 17, 2015 · 9 comments

Comments

@drone1
Copy link

drone1 commented May 17, 2015

Added to sass in version 3.1.6:

When set to true, emit a full trace of imports and mixins before each selector. This can be helpful for in-browser debugging of stylesheet imports and mixin includes. This option supersedes the :line_comments option and is superseded by the :debug_info option. Automatically disabled when using the :compressed output style.

@xzyfer
Copy link
Contributor

xzyfer commented May 27, 2015

No plans at the moment.

@xzyfer xzyfer modified the milestone: 3.4 May 27, 2015
@drone1
Copy link
Author

drone1 commented May 27, 2015

Would you help me understand why not? Seems like a lot of what people complain about with regard to mixins being difficult to debug goes away if you have a feature like this.

On Wed, May 27, 2015 at 12:16 AM, Michael Mifsud notifications@github.com
wrote:

No plans at the moment.

Reply to this email directly or view it on GitHub:
#1222 (comment)

@xzyfer
Copy link
Contributor

xzyfer commented May 27, 2015

Currently you are the only person asking for this. This issue is the first time I've heard of this feature. These two things tell me this is a very low priority. Certainly lower than getting feature parity with Ruby Sass.

We may eventually get to this but it's not a priority for anyone. We're open to pull requests.

@drone1
Copy link
Author

drone1 commented May 27, 2015

Roger that. Thanks.

On Wed, May 27, 2015 at 3:57 PM, Michael Mifsud notifications@github.com
wrote:

Currently you are the only person asking for this. This issue is the first time I've heard of this feature. These two things tell me this is a very low priority. Certainly lower than getting feature parity with Ruby Sass.

We may eventually get to this but it's not a priority for anyone. We're open to pull requests.

Reply to this email directly or view it on GitHub:
#1222 (comment)

@mgreter
Copy link
Contributor

mgreter commented Jan 9, 2016

I think we should close this. IMO this would first need to be supported by ruby sass.

@xzyfer
Copy link
Contributor

xzyfer commented Jan 12, 2016

This issue description suggests this is in Ruby Sass. Haven't confirmed.

@mgreter
Copy link
Contributor

mgreter commented Jan 12, 2016

If it is then my bad! Can someone confirm?

@mgreter mgreter mentioned this issue Apr 6, 2016
12 tasks
@mgreter
Copy link
Contributor

mgreter commented Apr 6, 2016

I created a collective ticket to keep track of this and other "non-urgent" feature requests, in order to keep the issue tracker a bit more clean for the more 1st aid issues. I would like to encourage everybody interested in this particular feature to add their comments into this closed issue anyway.

Thanks for your understanding and your contribution!

@mgreter mgreter closed this as completed Apr 6, 2016
@dertieran
Copy link

Just wanted to add my +1 for this feature.

Not sure what you consider as "supported by Ruby Sass".
You can't add it as a command line option (I think), but it is supported by sass.
I used it with compass for example.

Would be awesome to have this in libsass because it really helps when using some mixins.

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

No branches or pull requests

4 participants