No need to have two separate fields. For now, let's just go with a single "number" field and later down the road we can adjust this if needed.
BONUS:
I totally forgot that we have the graphql-scalar plugin. So while you're at it, please document it as well.
Just create a new entry here: https://docs.webiny.com/docs/api-development/plugins-reference
@Pavel910 For this one, we're gonna need a separate Number type for the GraphQL schema I'd say. It's either that or the user will have to select the number type in field options.
What do you think?
Some good info here - https://www.apollographql.com/docs/apollo-server/schema/scalars-enums/
Also, check this to see how you can add new scalars (@Ashu96): packages/graphql/src/createSchema/prepareSchema.ts:29
@doitadrian I think a custom scalar type for GQL is actually a good idea 馃憤
Most helpful comment
@doitadrian I think a custom scalar type for GQL is actually a good idea 馃憤