commandlineparser / commandlineparser/commandline

Bad format doesn't contain a lot of info

Open
#921 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
4.8k
Forks
478
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If a conversion in the constructor of a datatype throws an error, only a very generic error is available:

> Option 'some option' is defined with a bad format.

**To Reproduce**
* Have a property of type DirectoryInfo
* Supply bad character (mostly happens by accident)
* Get general error

**Expected behavior**
There are some options:
1. Add the used parameter to the BadFormatConversionError type so the bad formatted input string can be shown in the custom help callback.
2. Catch TargetInvocationException and add the inner exception to the BadFormatConversionError
3. Show a message with the message of the exception, especially when the exception is an ArgumentException.
It would then read something like 'Option 'i, input' is defined with "Invalid;Path" which is a bad format: Illegal characters in path.'

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.