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

Handle type errors when incorrect datatypes are used for all user-specified fields #16

Open
evinism opened this issue Dec 4, 2020 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@evinism
Copy link
Owner

evinism commented Dec 4, 2020

Examples include at least:

  • Specifying non-sets for tag_sets
  • Specifying non-strings in a tag_set
  • Specifying non-string paths for input_paths or output_paths
  • Specifying non-iterables for fileset:: prefixed tags.
@evinism evinism added the enhancement New feature or request label Dec 4, 2020
@evinism evinism added this to the Production-Ready Release milestone Dec 4, 2020
@evinism evinism added the good first issue Good for newcomers label Dec 4, 2020
@evinism evinism removed this from the Production-Ready Release milestone Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant