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

Add TypeMismatch value to InputInt and InputFloat #5

Open
HadrienMP opened this issue Jan 26, 2023 · 1 comment
Open

Add TypeMismatch value to InputInt and InputFloat #5

HadrienMP opened this issue Jan 26, 2023 · 1 comment
Assignees
Labels
breaking bug Something isn't working

Comments

@HadrienMP
Copy link

I did an Ellie to showcase a view validation oddities : https://ellie-app.com/kPP3jMh9w3Ja1

And I could not get the validation to work with only a min and no max.

@georgesboris
Copy link
Contributor

Jeezzz - sorry for taking this long see this @HadrienMP !

I believe the first two use cases were already addressed in a post-launch update or at least I haven't been able to replicate them (in the Ellie they're correctly invalidated when writing -1 and 11)

The last should indeed return an error! I'll make sure to patch it this week :) Thanks for reporting the problem!

@georgesboris georgesboris added the bug Something isn't working label Apr 13, 2023
@georgesboris georgesboris self-assigned this Apr 13, 2023
@georgesboris georgesboris changed the title InputInt validation is inaccurate Add TypeMismatch value to InputInt and InputFloat Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants