Celenium URL in BlockResponse doc + Unreleased changelog: /blocks/ → /block/#64
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Summary
Doc-only follow-up to ligate-explorer#41. The `BlockResponse.da_block_height` doc comment and the Unreleased changelog entry both referenced the wrong Celenium URL pattern: `/blocks/{height}` (plural) 404s, the right one is `/block/{height}` (singular). User caught it on the live explorer.
No behavior change — the api just returns the bare integer; URL composition is fully explorer-side. This PR keeps our docs honest so the next person reading the field's doc comment doesn't propagate the bad pattern.
Changes:
Test plan