-
Notifications
You must be signed in to change notification settings - Fork 37
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
unquote piped into unquote results in invalid unquote/2
invocation
#51
Comments
Heya, thanks for the issue. This doesn't look like something we'll fix in Styler. Sometimes when it makes kaboomy code, it's a good chance to zoom out and see if things can just be written different -- kind of like when the formatter makes code look weird. In this case, I'd suggest using |
unquote/2
invocation
That's not possible in the place that I extracted the code from, but I understand your point of there are other ways to write this. (this is from code generation path that produces code from a From experience with black/clang-format on large code bases I can tell you that you need to either focus on never producing broken code, or allow configuring styler in specific cases. TLDR: You should follow Linus' golden rule:
|
thanks for the input elliott, but having styler style code inside of quote is quite intentional - we like to keep all our code consistent. that said, we're very supportive of people forking the library and making the tool their own. |
while we don't want to disable styler in quotes, making it work with the idea that some |
Totally, that was simply the easiest tactical fix I could see, since creating quoted piped code wasn't that common. Thanks for the even better solution! |
Versions
Example Input
Stacktrace / Current Behaviour
That produces:
The text was updated successfully, but these errors were encountered: