Skip to content

No machine-readable version, so a consumer cannot check the JSON contract #33

Description

@lefoulkrod

jsonContract exists so a caller can check the shapes it was built against before trusting any other output. There is no way to read it.

$ omnideck --version
omnideck version dev (none) built unknown

Prose only, and it does not mention the contract at all. omnideck version is not a command.

Suggestion

Make --version --json emit the version, commit, build date and jsonContract. A consumer can then check one number at startup and refuse, or degrade, rather than misparsing output from a version it does not understand — which is the entire reason the constant is there.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions