Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nullable<string> on required:true #17

Open
dara-rockwell opened this issue Nov 23, 2022 · 1 comment
Open

Nullable<string> on required:true #17

dara-rockwell opened this issue Nov 23, 2022 · 1 comment

Comments

@dara-rockwell
Copy link

dara-rockwell commented Nov 23, 2022

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

@dara-rockwell
Copy link
Author

@justsml Any chance we can get a fix for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant