Skip to content

Downstream packages to start requiring type-specific attributes #126

Description

@gracecodes144

As per the discussion in chop-dbhi/data-models-service#20, the "reasonable default" behavior for missing attributes on types is causing problems and, frankly, seems hackish. These files should be the single source of truth and there shouldn't be a default behavior buried in some downstream package that determines field type attributes.

We need to fill in desired lengths, precisions, scales, etc across the repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions