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: Treat out-of-version fields as optional and decode if provided #10

Merged
merged 1 commit into from
Mar 6, 2025

Conversation

phsym
Copy link
Collaborator

@phsym phsym commented Mar 6, 2025

If a field is given while it does not belong to the current protocol version there's no reason not to decode it still. The request stays valid.

@phsym phsym added the enhancement New feature or request label Mar 6, 2025
@phsym phsym requested a review from a team as a code owner March 6, 2025 16:15
If a field is given while it does not belong to the current protocol version
there's no reason not to decode it still. The request stays valid.

Signed-off-by: Pierre-Henri Symoneaux <[email protected]>
@phsym phsym force-pushed the dev/phsym/optinal_outversioned_fields branch from aa61b8d to 42d878c Compare March 6, 2025 16:43
@phsym phsym merged commit cb4fafd into main Mar 6, 2025
3 checks passed
@phsym phsym deleted the dev/phsym/optinal_outversioned_fields branch March 6, 2025 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant