-
Notifications
You must be signed in to change notification settings - Fork 301
feat(lazer): add new formats to protocol #2414
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
writer.write_u32::<BE>(EVM_FORMAT_MAGIC)?; | ||
writer.write_u32::<LE>(EVM_FORMAT_MAGIC)?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this a breaking change? How does the current contracts in EVM that expect BE work with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a breaking change because I changed the constant value.
lazer/sdk/rust/client/Cargo.toml
Outdated
|
||
[dependencies] | ||
pyth-lazer-protocol = "0.5.0" | ||
pyth-lazer-protocol = { path = "../protocol", version = "0.5.0" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doesn't this break the publishing to cargo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, cargo is smart enough to remove paths on publish.
I think you should increase the protocol version too. |
Bumped protocol version. |
Message
enum for ser/deserializing any message type.BinaryWsUpdate
for ser/deserializing binary WS updates.I wanted to deprecate
parsed
in router API and replace it withformats: ["json"]
but unfortunatelyparsed
is true by default to we can't easily deprecate it. We can remove it when we do a breaking change and go for a/v2/..
endpoint.Tested WS client against a prod router to verify no breaking changes. Tested in tilt for new formats.