Skip to content
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

version field is confusing #16

Open
sellout opened this issue Nov 28, 2023 · 0 comments
Open

version field is confusing #16

sellout opened this issue Nov 28, 2023 · 0 comments

Comments

@sellout
Copy link
Contributor

sellout commented Nov 28, 2023

Multiple times now I have forgotten that the version field in a schema refers to the version of the schemas schema, and is not a version number for the schema that is being defined.

That sentence is confusing, too, so let me try again. When I modify schemas.projectConfigurations I am tempted to increment schemas.projectConfigurations.version, but that is not the right thing to do.

I don't have a great suggestion, but schemasVersion might be an improvement (note that it's plural, as schemaVersion doesn't seem any less confusing than version).

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

No branches or pull requests

1 participant