-
Notifications
You must be signed in to change notification settings - Fork 21
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
Proper Error
types for the crate
#386
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,51 @@ | ||
use crate::limit::ConditionParsingError; | ||
use crate::storage::StorageErr; | ||
use thiserror::Error; | ||
use std::convert::Infallible; | ||
use std::error::Error; | ||
use std::fmt::{Display, Formatter}; | ||
|
||
#[derive(Error, Debug, Eq, PartialEq)] | ||
#[derive(Debug)] | ||
pub enum LimitadorError { | ||
#[error("error while accessing the limits storage: {0:?}")] | ||
Storage(String), | ||
StorageError(StorageErr), | ||
InterpreterError(ConditionParsingError), | ||
} | ||
|
||
impl Display for LimitadorError { | ||
fn fmt(&self, f: &mut Formatter<'_>) -> std::fmt::Result { | ||
match self { | ||
LimitadorError::StorageError(err) => { | ||
write!(f, "error while accessing the limits storage: {err:?}") | ||
} | ||
LimitadorError::InterpreterError(err) => { | ||
write!(f, "error parsing condition: {err:?}") | ||
} | ||
} | ||
} | ||
} | ||
|
||
impl Error for LimitadorError { | ||
fn source(&self) -> Option<&(dyn Error + 'static)> { | ||
match self { | ||
LimitadorError::StorageError(err) => Some(err), | ||
LimitadorError::InterpreterError(err) => Some(err), | ||
} | ||
} | ||
} | ||
|
||
impl From<StorageErr> for LimitadorError { | ||
fn from(e: StorageErr) -> Self { | ||
Self::Storage(e.msg().to_owned()) | ||
Self::StorageError(e) | ||
} | ||
} | ||
|
||
impl From<ConditionParsingError> for LimitadorError { | ||
fn from(err: ConditionParsingError) -> Self { | ||
LimitadorError::InterpreterError(err) | ||
} | ||
} | ||
|
||
impl From<Infallible> for LimitadorError { | ||
fn from(value: Infallible) -> Self { | ||
unreachable!("unexpected infallible value: {:?}", value) | ||
} | ||
} |
Oops, something went wrong.
Oops, something went wrong.
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.
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.
nit:
out of curiosity, why do we need to add this implementation?
When I apply this patch, it is not needed.
Not arguing to change it, just curiosity.
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.
When you pass an iterator of
Condition
which areTryFrom
... butInfallible
.It'll go away, when I deal with the rest of the refactoring, but yeah... It is perfectly fine to pass
Condition
s right in theLimit
that you know cannot fail.