Skip to content

Centralize TypeScript model validation schemas in one place #9

Description

@frawleykid

We use input validation libraries to enforce the shape and constraints of artifact metadata, however that logic is currently duplicated between services. We should define that input validation schema in one place—probably the same repo as in #8—and then import it everywhere as git dependencies.

The most comprehensive input validation schema is defined here, so we should use that one. However, if other schemas impose additional constraints, we should include those as well.

The only other schema that comes to mind is this one.

Also see #10.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Task.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions