-
Notifications
You must be signed in to change notification settings - Fork 4
Proj0217: Enable requiring license acceptance #91
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
Conversation
|
I like this rule a lot. I'm wondering though, if there reasons to deviate, and if that is case, if allowing an explicit false is the best way to do so. We still can advise in the documentation to set it to true, but only warn when not set. If people added |
|
And may be add a screenshot to Markdown what the result is. |
Corniel
left a comment
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.
Besides the remarks made, I think this is a nice addition to our rules.
| this feature by setting `<PackageRequireLicenseAcceptance>` to `true` | ||
| ensures consumers of your package are given this prompt when trying to install | ||
| your package. However, if you don't explicitly define this, users will not be prompted | ||
| even if you would have liked them to. |
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.
[LanguageTool] reported by reviewdog 🐶
Did you mean “had liked”? (IF_WOULD_HAVE_VBN[1])
Suggestions: had liked
Rule: https://community.languagetool.org/rule/show/IF_WOULD_HAVE_VBN?lang=en-US&subId=1
Category: GRAMMAR
Documentation for dotnet-project-file-analyzers#342