-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Enhancement: Add Support for Floating Point Number Field #523
Comments
Thanks @LucasNeuhausDev for the suggestion. |
To have better Here is an example: {
"title": "Float field",
"name": "float",
"type": "number",
"numberOptions": {
"isDecimal": true,
"min": 0,
"max": 100,
"step": 0.01
}
} This way, you are able to specify more than only if it is a decimal value. You'll also be able to set the |
You'll be able to test it out in the latest BETA version. |
Exactly what I was looking for ♡. I came across the project via the livestream from you and James Q Quick and added it to my side project while watching the Stream. I will check out the Beta! |
I am currently working on a project where I need to store geolocations in my .mdx files as lat and lng fields.
Because lat and lng coordinates are floating point numbers and can be negative, the current number field type does not work.
I would love to either add a separate float field type or allow a numberFormat or similar field that allows to specify what number type is expected.
Expressing these as a string and then parsing them works, but is not ideal.
I think this would not only be beneficial for my use case but for a lot more.
The text was updated successfully, but these errors were encountered: