Repository navigation
Update '400 out_of_range' error description - #122
Merged
Masa8106 merged 1 commit intoOct 13, 2026
Merged
Conversation
Masa8106
requested review from
eric-murray and
grgpapadopoulos
as code owners
September 14, 2026 17:08
albertoramosmonagas
approved these changes
Sep 17, 2026
albertoramosmonagas
left a comment
albertoramosmonagas
left a comment
Contributor
There was a problem hiding this comment.
LGTM, only one note:
Because of this PR, when you update to the release, you'll likely need to define a specific schema for the error response; otherwise, it will be overwritten by the standardized model if you reference the common schema. It's a cosmetic change, in any case.
Contributor
Author
|
@albertoramosmonagas |
eric-murray
approved these changes
Oct 13, 2026
grgpapadopoulos
approved these changes
Oct 13, 2026
This file contains hidden or 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
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.
What type of PR is this?
What this PR does / why we need it:
Update the description of the
400 out_of_rangeerror in the API definition to explicitly include the future date validation case for better clarity.Which issue(s) this PR fixes:
Fixes #121
Special notes for reviewers:
None
Changelog input
Additional documentation
None