Doc: Reorder schema tables with dynamic keys first #3216
Merged
Conversation
This file contains 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
github-actions
bot
added
state: Documentation role Updated
role: eos_designs
4 tasks
gmuloc
approved these changes
Oct 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change Summary
Reorder schema tables with dynamic keys first
Proposed changes
In schema based documentation tables/yaml the order of keys was static keys first and then dynamic keys, but every place where we combine the two types in a single table, the primary input method would be the dynamic key.
This PR changes the order of keys in the schema tables to be dynamic keys first.
How to test
Check read-the-docs link for this PR.
Checklist
User Checklist
Repository Checklist