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