Serialize structure members in schema order, not declaration order - #1344
Open
adwsingh wants to merge 1 commit into
Open
Serialize structure members in schema order, not declaration order#1344adwsingh wants to merge 1 commit into
adwsingh wants to merge 1 commit into
Conversation
mtdowling
reviewed
Aug 30, 2026
| boolean isError = shape.hasTrait(ErrorTrait.class); | ||
|
|
||
| for (var member : shape.members()) { | ||
| for (var member : CodegenUtils.getSortedMembers(shape)) { |
Member
There was a problem hiding this comment.
Does this alphanumerically sort structure and union members? Or does it return those in model order / idx order if available?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What behavior changes?
Serialize structure members in schema order, not declaration order
Why is this change needed?
So that adding changing the order of fields in the model doesn't change the order of serialization.
How was this validated?
List tests added, benchmarks run, or manual verification performed.
What should reviewers focus on?
Point reviewers to the files or sections that contain the interesting logic.
Additional Links
Related issues, design docs, or prior art.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.