Skip to content

Nullable<string> on required:true #17

Description

@dara-rockwell
KEY: {
    required: true
}
  • Typescript is complaining that the type is still Nullable<string> instead of string
  • It appears that autoConfig is trying to figure out what the type is based upon default, but if there is no default then it presumes it can be Nullable even thought required is set to `true.

When running tests, at runtime we receive the following error as well:

ERROR: Found 1 Config Problem(s)!

    Fix the following 1 issue(s). (tip: try '--help' output for more details.)

      - Required: KEY invalid_type

This error is resolved by adding default: '' to the config

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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