Closed rainman400 closed 1 month ago
@rainman400 thanks for reporting this, we will look into supporting objects as component values.
BTW, by using the value: string.valued.default('')
operator, you are "telling" FormEngine that the default value is a string.
@rainman400
We are working on implementing a plain object as a data type. Could you share your use case for this feature? RSuite dropdowns support passing a value as an object with a shallow check for the value. Although it's not documented well.
yeah thats true.
I want to use an MUI dropdown which actually doesn't work the same way sadly. It does a check for the value as object, and throws an error.
To reproduce what I am facing, you can load the MUI dropdown the same way we load the RSuite dropdown. Alternatively, I have submitted a test repo a couple of months ago which can be used to quickly reproduce it.
Thank you! We will verify the MUI integration.
Both MUI and RSuite support passing values as either primitives or objects.
However, in RSuite, before version 5.50, setting the value as an object is not functional. This feature will necessitate an RSuite upgrade, so please be prepared.
Out of the box, these libraries are capable of handling primitive values combined with simply shaped options ({ label, value }: { string, string }).
Object values are handled differently in each library. Please check the demo for more details.
This looks great.
How does the integration into formbuilder work for this as a custom component?
There is some documentation here about using "valued" to let the component know that the custom component contains a value: https://formengine.io/documentation/custom-components#custom-component-containing-data
I was wondering how this would work for objects. I know its possible, since the dropdown component from rComponentSuite contains the value in this format, I am just not sure how to translate that into a custom component that would have a similar structure.
For more info: