Skip to content

Conversation

@suuuuuuminnnnnn
Copy link

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Docs
  • Other... Please describe:

What is the current behavior?

The Microservices MQTT transport documentation currently only describes configuring a global subscribeOptions (including qos) for all subscriptions.
It does not mention that QoS can be overridden per pattern/handler.

Issue Number: N/A

What is the new behavior?

The MQTT transport docs now include a small section describing how to override the subscription QoS per pattern/handler using extras.qos.
This showcases the feature added in nestjs/nest and clarifies that:

  • when extras.qos is provided, it overrides the QoS for that pattern
  • when not provided, the global subscribeOptions remains the default

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@kamilmysliwiec
Copy link
Member

Excellent! Could you please revert changes made to the lock file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants