-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add public option to embedded support for enums #1187
Conversation
@@ -11,6 +11,8 @@ | |||
<CsWinRTWindowsMetadata>10.0.19041.0</CsWinRTWindowsMetadata> | |||
<SimulateCsWinRTNugetReference>true</SimulateCsWinRTNugetReference> | |||
<CsWinRTGenerateProjection>true</CsWinRTGenerateProjection> | |||
<!-- Will expose enums as public in the projection |
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.
Do we want a test or something for this option?
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.
I think it's fine to leave testing this particular case to manual testing. We'd need another library for the different projection, plus the bells and whistles. I think the impact of these changes is low enough to not warrant such additional testing infrastructure.
8de9055
to
d4d23ff
Compare
In trying to enable PowerShell's AppX module, we found that some of the commands shipped within the module have options. These command line options are based on projected enum values, and the existing embedded support made those enums private to the module. There's no harm in exposing enums since they're simple objects, so we support public enums now.