Skip to content

[BREAKING] no default schema #171

@jkowalleck

Description

@jkowalleck

caused by #163 / #164

proposal / expected outcome

  • do not use a default schema at all
  • rename DEFAULT_SCHEMA_VERSION to LATEST_SUPPORTED_SCHEMA_VERSION
  • there is no defaulting or magic when it comes to SchemaVersions. Users have to input a valid value..

motivation:

  • no more breaking changes, when a new schema version is added. they are just features the users can plug.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions