Expected behavior Two separate instances of an MdbTablePaginationComponent should receive different instances of MdbTableService when they are in separate modules.

Actual behavior Two separate instances of an MdbTablePaginationComponent receive the same instance of MdbTableService despite being in separate modules with those modules each being resgitered as providers of MdbtableService.

Resources (screenshots, code snippets etc.)

You can see in the attached image that I have a parent module which holds the TabContainerComponent whilst the content of the two tabs are filled with components from different modules, for the sake of the question lets call them Tab1Module and Tab2Module. Each of these modules have a table showing data. For good segregation of responsibility, the table filters, the table itself and the pagination have each been segregated into their own container components (I don't want the pagination to be scrolling along with the table when on mobile). However, due to the MdbTablePaginationComponent requesting an injected instance of the MdbTableService, they both get the same one, resulting in problems with the numbers. Currently the respective service inside each of the tab modules hold all logic, so MdbtableService is injected into both Tab1Service and Tab2Service, however, these also receive the same instance. Am I injecting the table service incorrectly?

I have appended the following code to each of the tab modules however this still does not work:

Tab1Module

 imports: [TableModule]    
 providers: [Tab1Service, MdbTableService],

Tab2Module

imports: [TableModule]    
providers: [Tab2Service, MdbTableService],

Any advice is much appreciated!