Would you please advise how dynamic modal render through modalService.show() is expected to work with lazily loaded modules?

Scenario #1:

• Import MDBBootstrapModule.forRoot() on App.Modules
• Import MDBBootstrapModule on layzily loaded modules
• Declare Modal component in lazily loaded modules with entryComponents

Result: Exception when invoking modalSevice.show()

ERROR Error: No component factory found for DeleteModalComponent.

Scenario #2: - Import MDBBootstrapModule.forRoot() on sharedModules - Import sharedModules on layzily loaded modules - Declare Modal component in lazily loaded modules with entryComponents

Result: Modal is rendered properly with modalService.show(). However, backDrop removal is not working when switching between different lazily loaded modules.

By looking into the source code, I saw it is tracking the modalService instance through constant modalService.config.ts.

Questions:

1. Is "modalService" supposed to be singleton? If it is, what is the designed pattern to inject the ref of modal component in lazily loaded modules?
2. If we should have individual instance of "modalService" in lazily loaded modules, how should we track the instance? It seems constant only have one instance tracked, and always points to the last modalService instance (which is the root casue of backDrop hiding is not working properly). Could we use DI in constructor of modalContainer.component.ts to pass in the modalService instance?

PS: I saw the initialism of modalService in modalContainer.component.ts constructor is commented out on latest v9.3.1 code (enter link description here), how the reference is built in such case?

Please advise, thanks!