Skip to content
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.

[🚧] Parse exceptions in optional command parameters are silently swallowed #269

Open
MarkL4YG opened this issue Feb 5, 2021 · 0 comments
Assignees
Labels
bug Something isn't working feedback wanted Extra discussion is needed

Comments

@MarkL4YG
Copy link
Member

MarkL4YG commented Feb 5, 2021

When a user provides an optional command parameter, any thrown exception is ignored. This causes unintended behavior with syntactical errors:
For example, numeric inputs silently fail when the provided number is exceeding the integer range.
Instead, the matcher should be allowed to indicate its willingness but inability to consume the parameter, causing an error to be reported to the user.

@MarkL4YG MarkL4YG added bug Something isn't working feedback wanted Extra discussion is needed labels Feb 5, 2021
@MarkL4YG MarkL4YG self-assigned this Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working feedback wanted Extra discussion is needed
Development

No branches or pull requests

1 participant