[BUG] Custom Component feature does not seem to work or is not documented well enough for people to use.
See original GitHub issueEnvironment
Please provide as many details as you can:
Form.io is getting a lot of support requests to figure out how to get the new Custom Components feature working in this library. This was contributed by a community member and therefore does not fall under the maintenance umbrella of our company Form.io.
We need to do one of two things:
-
Remove that feature from this module so that Form.io can continue to support this module.
-
Move that contribution into the developers own repository.
-
Write more comprehensive documentation on how to get Custom components working with this new feature.
-
Hosting type
- Form.io
- Local deployment
- Version:
-
Formio.js version:
-
Frontend framework:
-
Browser:
-
Browser version:
Steps to Reproduce
Expected behavior
Observed behavior
Example
If possible, please provide a screenshot, live example (via JSFiddle or similar), and/or example code to help demonstrate the issue.
For code or form JSON, please enclose in a code block:
// your code here
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
The Angular wrapper for Custom Components still working, see: https://angular-formio-custom-demo.netlify.com/ (angular-formio version 4.5.1 used there)
But there is an other independent example, the checkmatrix, which is a JS-based example, and actually that doesn’t work for me either, that’s why we created our version.
Also the Angular wrapper may raise other questions, like custom templates, custom edit form or custom nested component, which weren’t involved in our scope.
I’m happy to document the current limitations and kindly ask the community to discover more solutions as we did: we reviewed and understand the formio.js implementation during our work.
If you receive too many support requests I’m also open to separate this functionality into own package.
Thanks for your support @merobal. We will keep this in place then, and hopefully the additional documentation will reduce the support burden on our end. Thanks again for your attention to this.