formio
[Custom Components] Do not work with lazy loading module
I've created a custom component, register this one in Root Module. Then I use formio builder in Lazy Module, it seem do not work.
But when I move registration custom component in to Lazy Module, it worked.
My issue: I have many Lazy Modules need to use formio, how I can do that? Should I register custom component on each lazy module? (have to change selector name)
I'm facing the same issue. Does anyone find out the way for this case? Thanks in advance.
I'm currently facing the same issue as well. I have all of my custom elements declared in one module that gets imported by multiple lazy loaded modules. The first time I go to each lazy loaded module the renderer works fine, but when I go back to a lazy loaded module for a second time it no longer works.
I have tried registering the custom elements in each lazy loaded module with a different selector and it still doesn't work.
Hello @SGhantous86
Thank you for your interest in Form.io!
In the future, please submit your questions to Gitter( located here: https://gitter.im/formio/formio) for our community support. We do offer Support Packages that are for training, support or development services. The hours can be used in one-hour increments at your convenience over a 90 day period. We will assign one of our senior developers to work directly with you in online sessions. If you are interested in learning more about our Support Packages, then please contact [email protected].
Thank you and have a great day!
@wag110894 Thank you for your reply. I had contacted FormIO support last week with my question and was told this is not something they could help with because I was creating custom elements from Angular components.
I will resubmit my question on gitter to see if the community can provide any support.
Hi @SGhantous86
Have you found the problem, because I am facing a similar problem.
We're currently addressing a backlog of GitHub issues, and as part of this effort, some inactive issues may be marked as closed. This isn't a dismissal, but a step toward more efficient tracking.
If you feel the issue is still relevant, please re-open and we'll ensure it gets the attention it deserves. Your understanding is appreciated as we work to enhance our open-source responsiveness.
