We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
init
set
The text was updated successfully, but these errors were encountered:
Fix commandlineparser#830
ce9cfc4
Successfully merging a pull request may close this issue.
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.The text was updated successfully, but these errors were encountered: