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.
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.
<!-- github-sync-id:1609346169 -->
This way, you are able to specify more than only if it is a decimal value. You'll also be able to set the min, max, and step value.
To have better `number` field support, there will be a new `numberOptions` setting coming which you can use in combination with your `number` field.
Here is an example:
```json
{
"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 `min`, `max`, and `step` value.
<!-- github-comment-id:1454699551 -->
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.
Just AMAZING work!
Exactly what I needed without looking for it 😃
I will check out the Beta!
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.
Just AMAZING work!
Exactly what I needed without looking for it 😃
I will check out the Beta!
<!-- github-comment-id:1454704935 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
Thanks @LucasNeuhausDev for the suggestion.
To have better
numberfield support, there will be a newnumberOptionssetting coming which you can use in combination with yournumberfield.Here is an example:
This way, you are able to specify more than only if it is a decimal value. You'll also be able to set the
min,max, andstepvalue.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.
Just AMAZING work!
Exactly what I needed without looking for it 😃
I will check out the Beta!