Skip to content

Support an option to not allow explicit null values for nullable fields. #183

Closed
@jakemac53

Description

@jakemac53

See InputSet as an example. Both of its fields are allowed to be null, but we don't really want users to be able to specify them as null explicitly in yaml. For instance, this should give an error:

targets:
  $default:
    sources:
      include:

include: there isn't treated any differently than if it didn't exist at all, and should probably be an error.

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