Skip to content

Keeping QCSchema in sync with QCElemental #68

@mattwelborn

Description

@mattwelborn

QCSchema lags behind what's actually implemented AND DOCUMENTED in QCElemental. The QCSchema docs are where people look for info, so this creates a misleading impression about what QCSchema is/does in practice.

Some possible solutions:

  1. QCSchema/docs is always what you get from running .schema()/autodoc on the myriad models in QCElemental
  2. QCElemental models represent schema in development, and from time to time we concretize its state into release versions of QCSchema.
  3. QCElemental models are not allowed to change until QCSchema changes.

My favorite option is 1. I'm okay with 2. I think 3 is a bad idea.

@dgasmith @bennybp

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