Skip to content

docs(microservices): document mqtt pattern qos#3383

Merged
kamilmysliwiec merged 3 commits intonestjs:masterfrom
suuuuuuminnnnnn:docs/mqtt-per-pattern-qos
Feb 4, 2026
Merged

docs(microservices): document mqtt pattern qos#3383
kamilmysliwiec merged 3 commits intonestjs:masterfrom
suuuuuuminnnnnn:docs/mqtt-per-pattern-qos

Conversation

@suuuuuuminnnnnn
Copy link
Copy Markdown
Contributor

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
Copy Markdown
Member

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

@suuuuuuminnnnnn
Copy link
Copy Markdown
Contributor Author

Sure — no problem. I accidentally included the lockfile changes.

I’ll revert package-lock.json back to the repository state and push an additional commit to this PR.

@kamilmysliwiec kamilmysliwiec merged commit a9a302e into nestjs:master Feb 4, 2026
4 checks passed
@kamilmysliwiec
Copy link
Copy Markdown
Member

lgtm

@suuuuuuminnnnnn suuuuuuminnnnnn deleted the docs/mqtt-per-pattern-qos branch February 4, 2026 10:47
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