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

Proposal: Use @function instead #9

Closed
lsycxyj opened this issue Apr 25, 2017 · 2 comments
Closed

Proposal: Use @function instead #9

lsycxyj opened this issue Apr 25, 2017 · 2 comments

Comments

@lsycxyj
Copy link

lsycxyj commented Apr 25, 2017

It would be less invasive like sass's @function instead of using a scope or a prefix to define the functions.

@seven-phases-max
Copy link
Owner

seven-phases-max commented Apr 25, 2017

Well, this would be quite burdening since then the plugin would have to parse/evaluate everything after @function till { on it's own (and either loose all of these features or implement them on its own thus turning itself in almost full-featured compiler).

But even w/o above considerations, the answer still would be "just no, sorry". (Less did not use at-rules for its own features for 8 years and I don't see any reason it should suddenly start to do that now. It's already fed enough with @ of variables. Besides there're practical reasons to not abuse at-rules - so it's actually pretty questionable which way is more invasive). So yes, abusing mixins is a hack, but it has its reasons.

@seven-phases-max
Copy link
Owner

seven-phases-max commented Apr 25, 2017

Closing as "out of the plugin scope" (The proposal is more suitable to discuss at less/less.js#538. And @function suggestion is already there, though all the con-args remain).

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

No branches or pull requests

2 participants