Skip to content

cac should enforce explicit parameters or ignore missing defaults #34

@timsearle

Description

@timsearle

cac shows lots of default fields as deleted in a diff, this can be confusing/disconcerting. It should either fail validation and expect defaults or actually cause a deletion (depending on other cac settings in play)

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