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

Decide how to handle serdect breaking change #830

Open
conradoplg opened this issue Jan 14, 2025 · 0 comments
Open

Decide how to handle serdect breaking change #830

conradoplg opened this issue Jan 14, 2025 · 0 comments

Comments

@conradoplg
Copy link
Contributor

serdect changed its encoding format in 0.3.0, which is breaking change for us.

Since we have a version field, we could introduce a new format version that uses 0.3.0, but we'd need to keep support for v0 format. This would involve a lot of code. So for now it seems better to simply keep using 0.2.0.

However, we might want to update if we determine that any of the reasons that caused serdect to upgrade are actually relevant to us (lower performance; possible variable timing in some cases, encoding inefficiency in some formats like MessagePack)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant