-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
mixin arguments can not be formatted #66
Comments
Mh yeah, I knew this would come someday 😌 Could you get around this in the meantime in the following way? - var nav = {
name: 'Solutions',
subnav: {
sublinks: [
{name: 'WISP', url: '#', icon:'wisp'},
{name: 'Fiber', url: '#', icon:'fiber'},
{name: 'MDU', url: '#', icon:'mdu'},
{name: 'Voice', url: '#', icon:'voice'},
{name: 'Cable', url: '#', icon:'cable'},
{name: 'Enterprise', url: '#', icon:'enterprise'}
]
}
}
+link(nav) It's tricky to implement this feature request, because it's multiline-javascript formatting within pug I may have time at the upcoming weekend |
I figured this would be a complicated implementation, so I am totally happy with the I wish I could help more with the implementation, but I unfortunately do not have much experience with creating linting rules (I'm guessing it's a fair amount of regex?), but I can certainly help test should you come up with anything. Thanks for the response! For anyone looking to use -
var nav = {
name: 'Solutions',
subnav: {
sublinks: [
{name: 'WISP', url: '#', icon:'wisp'},
{name: 'Fiber', url: '#', icon:'fiber'},
{name: 'MDU', url: '#', icon:'mdu'},
{name: 'Voice', url: '#', icon:'voice'},
{name: 'Cable', url: '#', icon:'cable'},
{name: 'Enterprise', url: '#', icon:'enterprise'}
]
}
}
+link(nav) |
Uff... we have a huge problem here :/ Lines 716 to 720 in 34f3a5d
Here we have So I will ask the author of pugjs to change the lexer to output a So sorry if this could take some time |
If I have the following formatted code:
It gets formatted to the following:
Is there any possible way to prevent this reformatting from happening, as it makes parsing the information far more difficult?
The text was updated successfully, but these errors were encountered: