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

fix(lazer-protocol): Update Latest Price Interface #2230

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

darunrs
Copy link
Contributor

@darunrs darunrs commented Jan 8, 2025

No description provided.

Copy link

vercel bot commented Jan 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 8, 2025 1:49am
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 8, 2025 1:49am
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 8, 2025 1:49am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
component-library ⬜️ Ignored (Inspect) Visit Preview Jan 8, 2025 1:49am
insights ⬜️ Ignored (Inspect) Visit Preview Jan 8, 2025 1:49am

Comment on lines +27 to +29
pub struct LatestPrice {
id: PriceFeedId,
prices: AggregatedPriceFeedData,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Previous response did not include IDs. In this case, I could either send over the map or conform it to a struct. I chose to use a struct instead of a map of id -> prices as I felt that made more sense to send over HTTP.

@darunrs darunrs merged commit 4621b98 into main Jan 8, 2025
9 checks passed
@darunrs darunrs deleted the fix-latest-price-api-interface-lazer branch January 8, 2025 16:34
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