Custom widget with HOC fails with < Error: Unsupported widget definition: object >
See original GitHub issuePrerequisites
- [ x ] I have read the documentation;
- [ x ] In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.
- Ideally, I’m providing a sample JSFiddle or a shared playground link demonstrating the issue.
Description
I have a custom widget that is wrapped in the react-redux “connect” HOC. Until recently it worked, but now fails with “Error: Unsupported widget definition: object”. I have tried reverting to old versions of rjsf, but to no avail.
Steps to Reproduce
- Create a custom widget
- Wrap in
connect({})(CustomWidget)
to observe the error
Version
Tried various versions:
- 2.0.0.alpha.1
- 1.8.1
- 1.4.0
- 1.2.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Custom Widgets and Fields - React Jsonschema form
Custom Widgets and Fields¶. The API allows to specify your own custom widget and field components: A widget represents a HTML tag for...
Read more >Custom Widgets for Android - HCL Volt MX Documentation
You can import and create your own custom widgets for the Android platform. Volt MX Irisplatform has defined a contract that any custom...
Read more >Metric Chart Widget - VMware Docs
The widget displays data based on the metrics that you select. ... You can create ad-hoc reports when analyzing metrics.
Read more >Unsupported Salesforce Objects and Fields in CRM Analytics
If you include an unsupported or inaccessible object in the sfdcDigest transformation, the dataflow fails at run time with an error message.
Read more >Problem - Rocket Software Documentation
TMON Change Manager for CICS TS System Definition Auditor ... More Properties (Widget Properties) ... Customize WRD Error Messages.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The same thing happened to me. The recent change was that you upgraded your react-redux package and they are using new react features that rjsf does not support yet. My temporary hack to make it work without reverting back to a lower version of react-redux was to wrap the connect call.
So, I wrote this:
Then you just do this:
That works as a temp fix.
Perhaps a bit clearer: