-
Notifications
You must be signed in to change notification settings - Fork 35
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
Update setters to accept default values #226
Update setters to accept default values #226
Conversation
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.
These changes do make the setters accept null values where needed, however because the setting values are no longer initialised by the Converter
class there are no longer effective defaults outside of the CLI interface.
As a minimal example, I would expect that creating a Converter and setting input & output would be enough to run .call()
with some standard settings assumed, however with this PR that method will now fail because a bunch of settings are null
and this is unhandled within the executor.
I would suggest that either we continue initialising these settings on creation, or the Converter should accept null
arguments when called and take that as a prompt to fetch the picocli default.
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.
All working well now, thanks
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.
This now requires conflicts to be merged as the version of Bio-Formats was bumped to 7.0.1. Then we should be in a good position to get this merged for 0.8.0
…to picocli-default-reset
...and define default values in the way that picocli expects them. Replaces #219, see discussion starting at #219 (comment).