-
Notifications
You must be signed in to change notification settings - Fork 628
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
powershell: Parse enum labels #3998
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3998 +/- ##
=======================================
Coverage 85.41% 85.41%
=======================================
Files 235 235
Lines 56647 56660 +13
=======================================
+ Hits 48384 48397 +13
Misses 8263 8263 ☔ View full report in Codecov by Sentry. |
Will take a look later today😁 |
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
About the letter for the kind, I gave a comment at #3571 (comment). About the name, |
@b4n, while you were absent, I added yet another overkill feature: parser versioning, which I have not documented well yet. This change extends the interface of the PowerShell parser. Therefore I would like you to include the following changes:
With this change, you'll see:
I want to say "thank you" to the person who wrote the zsh-completion rules for u-ctags. |
bad24b7
to
370de0f
Compare
I switched to @masatake I added your patch (adjusting for the leading space vs. tabs), under your name -- home that's OK. |
Thank you. |
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_enum?view=powershell-7.4 Co-Authored-By: Masatake YAMATO <yamato@redhat.com>
370de0f
to
2686322
Compare
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_enum?view=powershell-7.4
If anybody with actual PowerShell knowledge could give this an overview that'd be great. @eht16 @kumarstack55 @iaalm maybe?
The thing that most likely might need changing is the kind name. I used the "common" name for this type of construct, but maybe a more PowerShell-y one would be better, I don't know.