Skip to content
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

feat!: get latest costs from api #170

Merged
merged 3 commits into from
Dec 24, 2024
Merged

Conversation

rymnc
Copy link
Member

@rymnc rymnc commented Dec 17, 2024

Extends the costs api to support fetching the latest cost entries

BREAKING CHANGE: new query parameter needs to be specified variant = specific | latest

@rymnc rymnc force-pushed the feat/latest-block-cost-endpoint branch from 3764648 to 284be7e Compare December 17, 2024 18:54
Base automatically changed from feat/fix-cost-request to master December 18, 2024 23:25
@rymnc rymnc force-pushed the feat/latest-block-cost-endpoint branch 2 times, most recently from c1ac8d6 to 3a17b4a Compare December 18, 2024 23:40
fix: fmt

chore: add test, incl finalized only

fix: serde for query string

test: more shenanigans with query string

test: more shenanigans with query string

fix: option error handling
@rymnc rymnc force-pushed the feat/latest-block-cost-endpoint branch from 3a17b4a to 0532a3c Compare December 18, 2024 23:41
@MujkicA MujkicA changed the title test(costs): get latest costs from api feat: get latest costs from api Dec 23, 2024
@MujkicA MujkicA changed the title feat: get latest costs from api feat!: get latest costs from api Dec 23, 2024
@MujkicA MujkicA marked this pull request as ready for review December 23, 2024 19:31
@MujkicA MujkicA requested a review from a team December 23, 2024 19:32
@MujkicA MujkicA merged commit ce9acbc into master Dec 24, 2024
13 checks passed
@MujkicA MujkicA deleted the feat/latest-block-cost-endpoint branch December 24, 2024 11:28
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.

3 participants