Skip to content

feat: add /extended/v2/block-tenures/:height/blocks endpoint #2285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 16, 2025

Conversation

rafaelcr
Copy link
Collaborator

@rafaelcr rafaelcr commented May 15, 2025

Adds a new endpoint under /extended/v2/block-tenures/:height/blocks so users can get blocks only for a specific tenure. This endpoint builds over the code for the v2 blocks endpoint so it also inherits cursor pagination.

A new route is created so we can open the possibility of adding a REST endpoint to get stats or data from a specific tenure as requested in #2148

Replaces #2144

Copy link

github-actions bot commented May 15, 2025

Vercel deployment URL: https://stacks-blockchain-fxcs8hq0g-hirosystems.vercel.app 🚀

Copy link

codecov bot commented May 15, 2025

Codecov Report

Attention: Patch coverage is 96.66667% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/api/routes/v2/block-tenures.ts 95.00% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

@rafaelcr rafaelcr changed the title feat: add tenure_height filter to blocks endpoint feat: add /extended/v2/block-tenures/:height/blocks endpoint May 15, 2025
Copy link
Member

@zone117x zone117x left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@rafaelcr rafaelcr merged commit f5c2e01 into develop May 16, 2025
26 checks passed
@rafaelcr rafaelcr deleted the feat/tenure-height-filter branch May 16, 2025 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants