[Fix] Best block extraction id in separate field in /blocks/at/{height} API method response
#2263
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.
This Closes #978
This PR updates the
/blocks/at/{height}endpoint to return a structured response that explicitly distinguishes the best block from forked blocks at a given height. This removes ambiguity in the API response and makes fork handling explicit for API consumers.Changes
API Logic
BlocksApiRoute.scalagetHeaderIdsAtHeightto return:{ "best": "blockId", "forks": ["forkId1", "forkId2"] }BlocksApiRouteSpec.scalabestandforksfields.OpenAPI Specification
openapi.yaml/blocks/at/{blockHeight}response schema to match the new structured format.