Improve validation.LimitError usages #6954
Merged
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.
What this PR does
This PR improves usages of
validation.LimitError
errors. It addresses the following problems found in the code:limiter.AddSeries()
,limiter.AddChunkBytes()
,limiter.AddChunks()
andlimiter.AddEstimatedChunks()
return an error of typevalidate.LimitError
. In some cases, the caller of those functions used to wrap the returned error intovalidation.LimitError
, although it was not necessary. In order to prevent this, the signature of the above mentioned methods has been changed fromfunc AddXyz(...) error
tofunc AddXyz(...) validation.LimitError
. This way we enforced that the only allowed errors returned by these functions are of typevalidation.LimitError
.validation.LimitError
is now an interface, instead of a struct as it used to be.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.