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
There is only information on what parameters the function takes, but nothing on what it returns and their types.
Doing a simple console log in your code gets you more info, but for this particular function for example there are two values - payload and value and unless I go inside the conform codebase there is no way for me to tell which are the parsed values and which is the raw values.
It is the same for most other functions useForm is another example.
useField has some very basic return info, but it is not presented in the best way. Just as in the Parameters section it is missing the type, is it a string, is it a boolean, is it a function, if it is a function what is the shape of that function.
The library looks great, so improving on those will make it even greater and easier to use.
The text was updated successfully, but these errors were encountered:
I feel this, I have been struggling for an hour with splitting the form into different components, I just want to pass the return type of fields.MY_FIELD.getFieldset() but I just can't seem to get it quite right
Describe the bug and the expected behavior
For example here: https://conform.guide/api/zod/parseWithZod
There is only information on what parameters the function takes, but nothing on what it returns and their types.
Doing a simple console log in your code gets you more info, but for this particular function for example there are two values - payload and value and unless I go inside the conform codebase there is no way for me to tell which are the parsed values and which is the raw values.
It is the same for most other functions useForm is another example.
useField has some very basic return info, but it is not presented in the best way. Just as in the Parameters section it is missing the type, is it a string, is it a boolean, is it a function, if it is a function what is the shape of that function.
The library looks great, so improving on those will make it even greater and easier to use.
The text was updated successfully, but these errors were encountered: