fix: update error in SignedEntity
to be more descriptive
#3233
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.
Summary
Closes #2930
The exact error described in the issue cannot happen anymore as that behavior was changed in v2.1.0.
PR #2959 updated the old behaviour and added an if case where the error message is used in an if statement. The issue with this is that the error value is lost when
ErrEntityNotFound
error is created. This creates a problem where the error inSignedEntity
are not descriptive enough whenremoteGet
function fails.This PR will:
NewEntityNotFoundError
which uses the error received byremoteGet
to create a new error.IsEntityNotFoundError
which is used in the if statement that checks if the error message contains anErrEntityNotFound
string.Release Note
Updated error in
SignedEntity
to be more descriptivecc @znewman01