Repository navigation
Accept chain hashes on /v2/beacons/ routes - #27
Merged
Merged
Conversation
Requests to /v2/beacons/{beaconID}/... whose beaconID is a 64-char hex
string now resolve as a chain hash, the same as the /v2/chains/ routes.
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.
Clients sometimes call
/v2/beacons/{id}/...with a chain hash instead of a beacon ID.createRequestMDnow treats a 64-char hexbeaconIDas a chain hash, so those requests behave like the matching/v2/chains/route instead of failing on an unknown beacon ID.Beacon IDs are never 64 hex characters, so no existing ID changes meaning.