-
Notifications
You must be signed in to change notification settings - Fork 46
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
Order JSON Schema keywords #1382
base: 1.2-dev
Are you sure you want to change the base?
Conversation
… relevant information first
… relevant information first
bb1a465
to
e488475
Compare
To resolve a conflict, I reverted, committed only the management command, merged with 1.2-dev, and then ran the pre-commit command. So, nothing will have changed - the merge was just easier to resolve this way without error. |
Hmm, merging this will conflict with several open PRs. I'll leave it open until they are merged. Then, I can do the same as I did before (revert, run pre-commit, commit). |
Adding blocked label, as I guess we'll want to do this once all other PRs are merged |
I explain the preferred order in the comments in the sort_keywords function.
No changelog entry as re-ordering keywords is not a normative change.