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
We're using the number fields to store longitude and latitude because we only need these values. In the front-end we us GraphQL to query between two numbers.
Steps to reproduce
Have a Numbers field, set to 16-20 decimals
Query the exact number
Query between 2 numbers with decimals
Expected behavior
In case 2: have the exact entry returned
In case 3: have the entry and others returned
Actual behavior
When using the exact number, an error show we can only use string, integer or boolean.
When using a simple comparison (>= or <=), it show the correct entry and more
When using a range, it shows none
Extra
Don't know if this is expected behaviour but the filter input doesn't incorporate the decimal setting from the Number field.
Craft CMS version
Craft 5.2.0
PHP version
8.2
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered:
Thanks for reporting those! Craft 4.10.2 and 5.2.2 are out with a fix for the condition rule bug (6b370d3) and 5.2.2 also includes a fix for the query param handling (#15227).
What happened?
Description
We're using the number fields to store longitude and latitude because we only need these values. In the front-end we us GraphQL to query between two numbers.
Steps to reproduce
Expected behavior
In case 2: have the exact entry returned
In case 3: have the entry and others returned
Actual behavior
Extra
Don't know if this is expected behaviour but the filter input doesn't incorporate the decimal setting from the Number field.
Craft CMS version
Craft 5.2.0
PHP version
8.2
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: