use YAML key order to determine header order#455
Merged
sinaatalay merged 5 commits intorendercv:mainfrom Oct 23, 2025
Merged
Conversation
Member
|
Wow, thank you, that's great. I'll merge it, but there's a conflict. |
IanHollow
force-pushed
the
header-order
branch
from
ceb1b69 to
202cb22
Compare
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.
This another approach to a previous PR #450 that I talked about in the previous approach I personally like this approach much better.
This PR allows for the order of the header fields to determine the order that appear on final output.