fix(solace-message-client): do not eagerly construct `SolaceMessageCl…

…ient`

Previously, the SolaceMessageClient was constructed during application startup. This caused problems if OAuth authentication was enabled and the access token provider depended on services that were only available after the application was started. Instead, the SolaceMessageClient is now constructed on first use.

closes #53

projects/solace-message-client/src/lib/solace-message-client.module.ts

@@ -75,7 +75,7 @@ import {provideLogger} from './logger';
 @NgModule({})
 export class SolaceMessageClientModule {
 
-  constructor(@Inject(FORROOT_GUARD) _guard: any, _solaceMessageClient: SolaceMessageClient /** eager construction */) { // eslint-disable-line @typescript-eslint/no-empty-function
+  constructor(@Inject(FORROOT_GUARD) _guard: any) { // eslint-disable-line @typescript-eslint/no-empty-function
   }
 
   /**

projects/solace-message-client/src/lib/solace-message-client.spec.ts

@@ -66,6 +66,15 @@ describe('SolaceMessageClient', () => {
       await expectAsync(solaceMessageClient.session).toBeResolved();
     });
 
+    it('should not eagerly construct `SolaceMessageClient`', async () => {
+      TestBed.overrideProvider(SolaceMessageClient, {
+        useFactory: () => {
+          throw Error();
+        },
+      });
+      expect(() => TestBed.inject(SolaceMessageClientModule)).not.toThrowError();
+    });
+
     it('should allow to disconnect and re-connect from the Solace message broker', async () => {
       const solaceMessageClient = TestBed.inject(SolaceMessageClient);
       await simulateLifecycleEvent(SessionEventCode.UP_NOTICE);