19.0.0

19.0.0 (2024-12-05)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 19 (e623821)

Chore

• solace-message-client: remove deprecated APIs (393c003)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 19 introduced a breaking change.

  To migrate:

  • Update your application to Angular 19; for detailed migration instructions, refer to https://v19.angular.dev/update-guide;
  • Update solclientjs to version 10.17.1.

• solace-message-client: Removing the deprecated APIs introduced breaking changes.

  The following APIs have been removed:

  • SolaceMessageClientModule.forRoot => register Angular Solace Message Client using provideSolaceMessageClient function instead;
  • SolaceMessageClientModule.forChild => register Angular Solace Message Client using provideSolaceMessageClient function instead;
  • OAuthAccessTokenProvider => use OAuthAccessTokenFn instead;
  • BrowseOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • ConsumeOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • ObserveOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • RequestOptions.emitOutsideAngularZone => replies are received in the zone in which subscribed to the Observable. To receive replies outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;

18.0.0

18.0.0 (2024-06-03)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 18 (bacf6aa)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 18 introduced a breaking change.

  To migrate:

  • Update your application to Angular 18; for detailed migration instructions, refer to https://v18.angular.dev/update-guide;
  • Update solclientjs to version 10.16.0;

17.1.0

17.1.0 (2024-05-14)

Features

• solace-message-client: deprecate class-based access token provider in favor of functional access token provider (94a3f0e)
• solace-message-client: provide function to set up Solace Message Client (d9be295)
• solace-message-client: receive messages in the zone in which subscribed for messages (944b10c)
• solace-message-client: support connecting to multiple Solace message brokers (c832b00), closes #71
• solace-message-client: support loading config asynchronously (1be10e6)

17.0.1

17.0.1 (2024-05-07)

Bug Fixes

• solace-message-client: support subscriptions with #share and #noexport (fa161bc)

17.0.0

17.0.0 (2023-11-21)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 17 (49b8c86), closes #68

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 17 introduced a breaking change.

  To migrate:

  • Update your application to Angular 17; for detailed migration instructions, refer to https://v17.angular.io/guide/update-to-latest-version;
  • Update solclientjs to version 10.15.0;
  • solclientjs now requires type definitions for node. In your tsconfig, add node to the types array in compilerOptions. If you have not specified types, no manual registration of node is required, since without types array all @types packages are included in the build.

16.0.0

16.0.0 (2023-05-17)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 16 (73a5edc), closes #60

Features

• testapp: improve accessibility of testing app (7f91a5c)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 16 introduced a breaking change.

  To migrate:

  • update your application to Angular 16; for detailed migration instructions, refer to https://v16.angular.io/guide/update-to-latest-version;
  • update solclientjs to version 10.13.0;

15.0.0

15.0.0 (2022-12-20)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 15 (4638ed2), closes #52

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 15 introduced a breaking change.

  To migrate:

  • update your application to Angular 15; for detailed migration instructions, refer to https://v15.angular.io/guide/update-to-latest-version;

14.0.1

14.0.1 (2022-11-23)

Bug Fixes

• solace-message-client: do not eagerly construct SolaceMessageClient (82f73ed), closes #53

14.0.0

14.0.0 (2022-08-16)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 14 (6c48828), closes #49

Features

• tryme: use Solace sponsored broker as default broker (f4879be)

Chore

• solace-message-client: remove deprecated API ObserveOptions#requestTimeout (813cf2d)
• solace-message-client: remove deprecated API SolaceMessageClient#enqueue (7f9125c)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 14 introduced a breaking change.

  To migrate:

  • update your application to Angular 14; for detailed migration instructions, refer to https://v14.angular.io/guide/update-to-latest-version;
  • update @scion/toolkit to version 1.0.0 using the following command: npm install @scion/toolkit@latest --save. Note that the toolkit was previously released as pre-releases of version 13.0.0 or older; for detailed migration instructions, refer to https://github.com/SchweizerischeBundesbahnen/scion-toolkit/blob/master/CHANGELOG_TOOLKIT.md

• solace-message-client: Removing the deprecated API ObserveOptions#requestTimeout introduced a breaking change.

  To migrate, use ObserveOptions#subscribeTimeout instead.

• solace-message-client: Removing the deprecated API SolaceMessageClient#enqueue introduced a breaking change.

  To send a message to a queue, use SolaceMessageClient#publish instead and pass the queue destination. The queue destination can be constructed using SolclientFactory as follows: SolclientFactory.createDurableQueueDestination('queue').

13.1.0

13.1.0 (2022-04-24)

Bug Fixes

• tryme: do not require username and password when authenticating via OAUTH (478d2b3)

Features

• solace-message-client: add API for OAUTH 2 authentication (8090648), closes #39
• solace-message-client: add API for request-response communication (dcd831d), closes #38
• solace-message-client: allow changing the log level (7ee0155)
• solace-message-client: migrate to "solclientjs" type definitions (7ce7212), closes #37

BREAKING CHANGES

• solace-message-client: migrating to "solclientjs" type definitions introduced a breaking change.

  To migrate:

  • install [email protected] using the NPM command line, as follows: npm install [email protected] --save
  • install @types/events using the NPM command line since required by solclientjs typings, as follows: npm install @types/events --save-dev
  • install @types/long using the NPM command line since required by solclientjs typings, as follows: npm install @types/long --save-dev
  • import solclientjs specific types from solclientjs instead of @solace-community/angular-solace-message-client
  • construct solclientjs specific objects via SolclientFactory instead of SolaceObjectFactory
  • construct SDTField via SDTField.create(...) instead of SolaceObjectFactory.createSDTField(...) factory method;
  • construct SDTMapContainer via new SDTMapContainer() instead of SolaceObjectFactory.createSDTMapContainer() factory method
  • when subscribing to a queue, you need to pass the queue spec via QueueDescriptor instance instead of an object literal, as follows:

    messageClient.consume$({
     queueDescriptor: new QueueDescriptor({type: QueueType.QUEUE, name: 'queue'}),
     queueProperties: undefined, // necessary until solclientjs changes it to optional
    });

  • when browsing a queue, you need to pass the queue spec via QueueDescriptor instance instead of an object literal, as follows:

    messageClient.browse$({
      queueDescriptor: new QueueDescriptor({type: QueueType.QUEUE, name: 'queue'}),
    });

  • For more information about known typedef issues, see issue/37