Skip to content

Write JSON Schema properties in the LinkML's declared order #45

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.

Sign up for GitHub

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

Merged
jdkent merged 1 commit into from
Oct 18, 2026
Merged

Write JSON Schema properties in the LinkML's declared order #45

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -326,6 +326,8 @@ parse = CoordinateParse.model_validate_json(path.read_bytes())

**Unique keys.** A class with a LinkML `unique_keys` carries `"x-unique-keys": [[slot, ...], ...]` on its definition, its own keys first and then inherited ones with each key's slots in declared order, and `study_schema.jsonschema.unique_keys(name)` returns them as a dict from class to tuples of slot names.

**Property order.** Each object's `properties` follow the LinkML's declared slot order, inherited slots included, rather than alphabetical order.

Every model forbids fields its schema does not declare, so a file written against another
version fails where it is read, naming the field, instead of losing what the reader does not
recognise. Each model module records the schema version it was generated from as `version`,
Expand Down
Loading
Loading