Skip to content

version field is confusing #16

@sellout

Description

@sellout

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions