-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add recommendations for coding styles #64
Conversation
cc @cidrblock |
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.
LGTM, its going to evolve over time, but this is a good start.
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.
Again good inputs, more formal comments than regarding the content.
Overall we're trying to align this section (and the roles one) to the overall pattern explanation/rationale/example, so if you could start to stick to it, that would be helpful, but on the other hand, the coding recommendations are generally very short so it's a lot of boilerplate...
Regarding the task names, I really hate having them start with a capital letter (only my play names start with a capital letter), but we can discuss this in the group.
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.
I have a few small suggestions but otherwise this looks good to me.
Approved in CoP meeting 2022-06-29 |
Draft of coding styles recommendations from ansible eng