Skip to content

Should there be type validation or is everything a string #8

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

Open
MartinHelmut opened this issue Sep 30, 2020 · 2 comments
Open

Should there be type validation or is everything a string #8

MartinHelmut opened this issue Sep 30, 2020 · 2 comments
Labels
feature Something new. question Further information is requested / general question.
Milestone

Comments

@MartinHelmut
Copy link
Member

For parameters there is currently a type option for parameter validation. This has many implication on how this should be validated, what types are supported and can this be influenced by the user? Currently there could be support for: string, integer, float, number (combination of integer and float). But then what about more specific types like "date", "url" and n-more types. The alternative could be that every parameter is a string for now. This will result in less issues and less thinking for the user.

@MartinHelmut
Copy link
Member Author

For now the only types are: string and and array of options as strings.

@MartinHelmut MartinHelmut added feature Something new. question Further information is requested / general question. labels Oct 11, 2020
@MartinHelmut
Copy link
Member Author

The type boolean was added naturally on implementing the script interpreter.

@MartinHelmut MartinHelmut added this to the Future milestone May 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new. question Further information is requested / general question.
Projects
None yet
Development

No branches or pull requests

1 participant