Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend websocket next documentation to explain when and when not to subscribe to a Uni or Multi #44556

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

cescoffier
Copy link
Member

Fix #42566

Copy link

github-actions bot commented Nov 18, 2024

🙈 The PR is closed and the preview is expired.

@cescoffier cescoffier force-pushed the websocket-next-subscription branch from 829a2ac to 60c79b6 Compare November 19, 2024 13:13

This comment has been minimized.

Copy link
Contributor

@mkouba mkouba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

docs/src/main/asciidoc/websockets-next-reference.adoc Outdated Show resolved Hide resolved
@cescoffier cescoffier force-pushed the websocket-next-subscription branch from 60c79b6 to 03a5ea7 Compare November 20, 2024 06:42
Copy link

quarkus-bot bot commented Nov 20, 2024

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 03a5ea7.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@mkouba mkouba merged commit 26db59d into quarkusio:main Nov 20, 2024
5 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.18 - main milestone Nov 20, 2024
@quarkus-bot quarkus-bot bot added the kind/enhancement New feature or request label Nov 20, 2024
@cescoffier cescoffier deleted the websocket-next-subscription branch November 22, 2024 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

be explicit/use examples in websocket.next docs when it comes to subscribe call for action
2 participants