Skip to content

Preserve ordering of schema for docs#111

Merged
JonoPrest merged 1 commit into
mainfrom
jp/preserve-schema-order
Aug 7, 2024
Merged

Preserve ordering of schema for docs#111
JonoPrest merged 1 commit into
mainfrom
jp/preserve-schema-order

Conversation

@JonoPrest

Copy link
Copy Markdown
Collaborator

No description provided.

@JonoPrest JonoPrest requested a review from DZakh August 7, 2024 15:52
@JonoPrest JonoPrest force-pushed the jp/preserve-schema-order branch from 27cd2b0 to 09688e6 Compare August 7, 2024 15:53
Comment on lines +14 to +16
"name": {
"description": "Name of the project",
"type": "string"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I looked at the code for schema rs and it will always order the keyword "description" first for it's own objects so we basically just have a name collision there. I don't think it's very important to change right now. Not sure if we should even keep description in the schema.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, I think it's not used in any way.

Comment on lines +14 to +16
"name": {
"description": "Name of the project",
"type": "string"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, I think it's not used in any way.

@JonoPrest JonoPrest merged commit b5af3fa into main Aug 7, 2024
@JonoPrest JonoPrest deleted the jp/preserve-schema-order branch August 7, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants