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
Current behavior:
We use the generate-typescript-typedefs command to generate our types. But we noticed an issue: When we choose the field type 'number' in storyblok the generated type will be string, which is very unexpected, since this is a very easy type.
Expected behavior:
The type of a field-type number should be number as well.
Steps to reproduce:
Create a new Storyblok Block, with one field type number. Save that block.
Use the generate-typescript-typedefs command to generate the types for this new block. Notice that the new field-type has the type string instead of number.
Current behavior:
We use the
generate-typescript-typedefs
command to generate our types. But we noticed an issue: When we choose the field type 'number' in storyblok the generated type will bestring
, which is very unexpected, since this is a very easy type.Expected behavior:
The type of a field-type
number
should benumber
as well.Steps to reproduce:
Create a new Storyblok Block, with one field type
number
. Save that block.Use the
generate-typescript-typedefs
command to generate the types for this new block. Notice that the new field-type has the typestring
instead ofnumber
.An example components.json schema:
And the related typings:
The text was updated successfully, but these errors were encountered: