-
Notifications
You must be signed in to change notification settings - Fork 388
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
PSSCriptAnalyzer Needs Rule Sets #383
Comments
Agree - and there was a discussion on what these should be named - previously was Profiles (agreed bad name and therefore changed) but changed to configuration - which I very much disagree with due to configuration being a keyword and I would be more suggestive to rename this (again) to RuleSet This is more generic and would be more better for discoverability with an additional about topic being packed with it |
Yeah given that the tool has "rules", PSScriptAnalyzer's default ruleset should contain only the rules that have a very high probably of indicating a real problem. I believe this will give the best "out of the box" experience and if users want more, well then the team should have more rulesets that the user can choose from. |
Agreed with @kilasuit here. I apologize for missing the conversation on Profile vs. Configuration as I would have been in favor of leaving the original parameter name (i.e. Profile), given the fact it's a breaking change. However, since we haven't properly documented or implemented any yet, I would also be open to a breaking change on the parameter name, but Configuration is absolutely confusing as a PowerShell keyword. Thoughts? |
I like RuleSet. If it looks like a duck and acts like a duck... |
Cool, we'll raise it on the call today and see if anyone has any objections. |
We need rule sets for minimum safety, basic design, recommended design, etc. When you start bringing in rules like mandating named parameters or placement of curly braces, you are way past the point where you should have started collecting them into sets.
The text was updated successfully, but these errors were encountered: