You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks. My first assumption was that the resolution range queryable is of type integer, but it's of type number. So this is certainly a bug. PRs are welcome.
The Search Filter Input prevents the user from entering floating point numbers for number fields.
Reproduce:
Add filter
Resolution range (m)
. This field is a number type that supports decimalsExpected Behaviour:
The user can type in any valid number
The text was updated successfully, but these errors were encountered: