allow using lazy loadable renderers in angular

[dsl400]

proposal to add possibility to use lazy loadable renderers

[netlify]

✅ Deploy Preview for jsonforms-examples ready!

Name	Link
🔨 Latest commit	5e32b15
🔍 Latest deploy log	https://app.netlify.com/sites/jsonforms-examples/deploys/6820b7fe3b08cd000806ce7f
😎 Deploy Preview	https://deploy-preview-2446--jsonforms-examples.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[CLAassistant]

All committers have signed the CLA.

[coveralls]

coverage: 82.517%. remained the same
when pulling 5e32b15 on dsl400:master
into 6637fb0 on eclipsesource:master.

[lucas-koehler]

Hi @dsl400 ,
thanks for the contribution!
What is you use case for this change? Usually, the number of renderers should be small enough to load them synchronously.
I ask because I'm a bit concerned that an asynchronous update method might lead to race conditions when being invoked frequently by the state subscription added in ngOnInit.

[dsl400]

I was hoping to migrate our existing code by loading some components as custom renderers until we have time to create schema for all our existing forms

[sdirix]

I don't think this PR is necessary. Instead of within JSON Forms you could await the renderers outside of JSON Forms and only render JSON Forms once they are resolved.

[dsl400]

I don't think this PR is necessary. Instead of within JSON Forms you could await the renderers outside of JSON Forms and only render JSON Forms once they are resolved.

Can you provide some technical arguments about why ?
Maybe it is something that I do not yet understand.

My argument is: It has no impact on existing functionality