-
Notifications
You must be signed in to change notification settings - Fork 109
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 whitespace in nginx templates #597
Conversation
The nginx templates were hard to read due to excessive whitespacing in the templates. It's not perfect, but these changes should clean things up quite a bit.
The generated config is much easier to read now:
My only concern is figuring out how to use those whitespace reduction techniques going forward (confession - I haven't mastered them :) ) Is there a set of rules/ guidelines we can have for our template writing? So that any developer can follow them, and any reviewer of future template changes can also follow them, and they both can arrive at similar result? I think another approach is just eliminate all empty lines. For example, during template generatation. |
@pleshakov It's definitely a bit finicky to get all the spacing correct, especially when trying to balance readability in the code using empty lines with readability in the rendered template. There may not be a perfect solution. Regarding the templating, this is how it works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The nginx templates were hard to read due to excessive whitespacing in the templates. It's not perfect, but these changes should clean things up quite a bit.
The nginx templates were hard to read due to excessive whitespacing in the templates. It's not perfect, but these changes should clean things up quite a bit.