Skip to content

Support full object definitions for valid values in schema #904

@tsalo

Description

@tsalo

Currently, valid values (i.e., enums) for objects in the schema are written as lists. However, in some cases, we also want to have each value defined, and perhaps even summarized in a separate table. As an example, take the channels file for MEG data. Each of the valid values for the type column has a description, which is currently rendered with a hardcoded table, but which could be incorporated into the schema directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestschemaIssues related to the YAML schema representation of the specification. Patch version release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions