Maciej Urbańczyk
Maciej Urbańczyk
PR https://github.com/asyncapi/website/pull/1261 @alequetzalli
Resolved by https://github.com/asyncapi/asyncapi-react/pull/621
@sambhavgupta0705 Sure, you can reuse code from https://github.com/asyncapi/asyncapi-react/pull/624
@ThibaudAV Hi! > I came across this Issues by chance and would like to know if it is still relevant ? whether it is still a proposal or whether work...
@ThibaudAV I was thinking to make it framework agnostic, as a separate DI package and then separate integrations for `react`, `vue`, even for some nodejs framework for backend application. I...
@sarisia Thanks for contribution!
@sarisia No problem! Yeah, it can be :) Please create issue and I will make PR. I would like to close as many issues as possible in the next few...
Maybe context like in React will resolve the problem? If Angular will treat modules also like components, then we can do something like: ```ts @NgModule({ selector: "some-module", providers: [SomeProvider1, SomeProvider2],...
@LayZeeDK Thanks for response! Yeah, I know about `NodeInjector`, but I had in mind that this syntax: ```html ...body ``` is actually this in current implementation: ```ts @NgModule({ declarations: [SomeComponent],...
`` should be renderer (based on module declaration), but in my idea is a problem, how to tell to Angular that definition (factory) of `` is `SomeComponent` (definition in TS...