feat(parsing): give serviceable parsing error details to users #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR #134 was, in my opinion, a missed opportunity to improve the diagnostics offered by `cron::error::Error` to users, which at the moment always displays as an unhelpful "Invalid expression: Invalid cron expression." string. Let's improve on that by displaying the underlying parse error instead, which is serviceable enough to know what the input was and what exactly went wrong parsing it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #134 was, in my opinion, a missed opportunity to improve the diagnostics offered by
cron::error::Errorto users, which at the moment always displays as an unhelpful "Invalid expression: Invalid cron expression." string. Let's improve on that by displaying the underlying parse error instead, which is serviceable enough to know what the input was and what exactly went wrong parsing it.