Skip to content

refactor(pyth-lazer-protocol): rename PublisherResponse -> ServerResponse #2293

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 1 commit into from
Jan 23, 2025

Conversation

tejasbadadare
Copy link
Contributor

rename PublisherResponse -> ServerResponse to better communicate that this is a message generated by the server.

Copy link

vercel bot commented Jan 23, 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 23, 2025 4:55pm
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 23, 2025 4:55pm
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 23, 2025 4:55pm
3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
component-library ⬜️ Ignored (Inspect) Jan 23, 2025 4:55pm
entropy-debugger ⬜️ Ignored (Inspect) Visit Preview Jan 23, 2025 4:55pm
insights ⬜️ Ignored (Inspect) Jan 23, 2025 4:55pm

@tejasbadadare tejasbadadare merged commit c2716a2 into main Jan 23, 2025
10 checks passed
@tejasbadadare tejasbadadare deleted the tb/lazer/rename_publisher_response branch January 23, 2025 17:04
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