Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Issue with map fields when clustered short options are disallowed
See original GitHub issueDescription
When clustered short options are disallowed with
CommandLine.setPosixClusteredShortOptionsAllowed(false)
specifying arguments for map fields as follows
-Pmyprop=myvalue
fails with the exception
picocli.CommandLine$UnmatchedArgumentException: Unknown option: -Pmyprop=myvalue
The space is now required between -P and the key-value pair.
-P myprop=myvalue //works
Is this the expected behaviour? IMO, map fields are different from other fields, and it would be useful to have the support for the former even when clustered short options are not allowed.
Version 3.3.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@MaryamZi No worries, glad to hear the current behaviour is ok.
Good idea to clarify the docs. I will add a note to the https://picocli.info/#_posix_clustered_short_options section.
@remkop sorry about the delay in responding. The current behaviour is OK, just wanted to clarify if this was the expected behaviour.
Should we maybe include this in the documentation too, since all possible ways of specification are mentioned in the example?
Thank you!