Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow private property options #830

Open
Saalvage opened this issue Jun 18, 2022 · 0 comments · May be fixed by #831
Open

Allow private property options #830

Saalvage opened this issue Jun 18, 2022 · 0 comments · May be fixed by #831

Comments

@Saalvage
Copy link

Saalvage commented Jun 18, 2022 •
edited

I think that private properties should be considered when reflecting to get all option properties.

This would allow for exposing a different interface for specifying options to the CLI and the code, which can often be beneficial.

It is already possible for the library to use a public property with a private init/set so this seems more like an oversight than anything else.
Saalvage added a commit to Saalvage/commandline that referenced this issue Jun 19, 2022
@Saalvage
Fix commandlineparser#830
ce9cfc4
@ericnewton76 ericnewton76 linked a pull request Sep 10, 2022 that will close this issue
Fix #830 - Recognize Option, Value and Usage attributes on private members #831
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #830 - Recognize Option, Value and Usage attributes on private members Saalvage/commandline
1 participant
@Saalvage