chore: add aex9 validation to v1 range endpoints #784
Merged
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
jyeshe
force-pushed
the
v1-validate-aex9-at-hash
branch
from
311da85
to
94237f0
Compare
jyeshe
force-pushed
the
v1-validate-aex9-at-range
branch
from
c681dae
to
ff50af4
Compare
sborrazas
approved these changes
Jul 11, 2022
jyeshe
force-pushed
the
v1-validate-aex9-at-range
branch
from
ff50af4
to
87a8a14
Compare
|
rebased... |
thepiwo
approved these changes
Jul 12, 2022
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.
Resolves #771