- Notifications
You must be signed in to change notification settings - Fork407
Make UseSingularNouns rule work on PowerShell Core#1627
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
SydneyhSmith commentedFeb 3, 2021
Ah unfortunately, the fact that the package is unlicensed does block us from accepting it |
bergmeister commentedFeb 3, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Ok, will contact the author if an MIT license or something similar can be added as it was probably not intentional by the author. Would the licence need to be on the NuGet package or just the source repo? |
bergmeister commentedFeb 7, 2021
@SydneyhSmith I updated it to use the |
SydneyhSmith commentedFeb 16, 2021
Thanks@bergmeister that package looks good to us |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
47150bf to9327e6fCompare1402a5e to5832be4Compare
Uh oh!
There was an error while loading.Please reload this page.
PR Summary
Fixes#1626
This uses the open source
Pluralize.NETNuGet package, which uses the MIT licence. The added payload is only 20KB once.Also enhance existing code to not construct
Pluralizationservicein foreach loop.PR Checklist
.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.