-
Notifications
You must be signed in to change notification settings - Fork 1
class rules should apply to plans as well #21
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
Comments
I miss it when working on Bolt plans in a VSCode with Puppet plugin! Though need to check carefully for any corner cases. E.g. direct |
Yes, not all checks apply to plans. But the majority. |
We don't believe plans have been fully reviewed in terms of style and semantics in the same fashion as the puppet language. |
@pmcmaw @jordanbreen28 not sure if this issue should be moved to https://github.com/puppetlabs/language-style-guide or kept open and referenced to an issue there? |
@bastelfreak we have moved this to the appropriate repository for that teams review. Thanks |
@danadoherty639 hey, do you have any update here? |
@bastelfreak this is on my todo list as ultimately this should come from the language steering group which as part of the changes to open source should be made up of community and Puppet inc reps |
Use Case
We've a lot of checks that apply to classes (and sometimes defined resources). For example the
parameter_order
check. It ensures that parameter without a value are listed before parameters with a value. I think those checks should apply to plans as well, but puppet-lint explicitly only checks classes and defined resources: https://github.com/puppetlabs/puppet-lint/blob/main/lib/puppet-lint/plugins/check_classes/parameter_order.rb#L8Describe the Solution You Would Like
Treat plans as classes and apply the same checks.
Describe Alternatives You've Considered
Additional Context
The text was updated successfully, but these errors were encountered: