-
-
Notifications
You must be signed in to change notification settings - Fork 871
streamline defaults with nginx #1661
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
base: master
Are you sure you want to change the base?
Conversation
|
Where you're making changes to every parameter, maybe also stop aligning the equals signs (just have one space of separation, like |
|
Do you mean only simple assignments or also parameter defaults? For my understanding see latest commit. |
For all class parameter lists, I think we shouldn't be aligning the equals signs. It just causes too many diffs when there are changes to the parameter lists. |
|
puppet style guide says otherwise: (You should however not take the examples too serious as they are displayed, there seems to be a HTML issue. So inspect the HTML source instead...) That taken into account the current state of the PR should be ok... |
|
That part of the style guide I don't think we should follow, especially for a module like this with large lists of parameters. See also voxpupuli/voxpupuli.github.io#322 |
|
ok, then everything should be fine now. |
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.
Minor thing, but not sure it's valuable to have nginx defaults in the comments, since the defaults can change.
Pull Request (PR) description
All parameters with feasible defaults in nginx itself become
Optional.Also fixes some minor type isssues.
This Pull Request (PR) fixes the following issues
Fixes #1660