ADR Proposal: Throws exception when future datetime is passed to current/historical APIs #406
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
Signed-off-by: Yasumasa Suenaga <[email protected]>
21 tasks
YaSuenag
changed the title
|
Seems like a good idea. To discuss on next meeting I guess. |
|
This a stale pull request. Please review, update or/and close as necessary. |
29 tasks
22 tasks
|
Shall we reopen this ? |
|
Sure, I think this proposal should go further. |
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.
Pull Request
#396
Summary
Propose to throw exception / return HTTP error status when future datetime is passed to current/historical APIs.
Changes
Add ADR about this topic. See ADR-0016 document in this PR for details.
Checklist
Are there API Changes?
No
Is this a breaking change?
No