Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 33dee6f

Browse filesBrowse files
committed
minor #20580 [Mercure] Adding hint for multiple topics (ThomasLandauer)
This PR was merged into the 6.4 branch. Discussion ---------- [Mercure] Adding hint for multiple topics Page: https://symfony.com/doc/6.4/mercure.html#subscribing Closes #20574 Closes symfony/mercure-bundle#71 Closes symfony/mercure-bundle#82 Info is taken from #20574 (comment) Commits ------- 3dca32e [Mercure] Adding hint for multiple topics
2 parents 6301562 + 3dca32e commit 33dee6f
Copy full SHA for 33dee6f

File tree

Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed

‎mercure.rst

Copy file name to clipboardExpand all lines: mercure.rst
+5Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -309,6 +309,11 @@ as patterns:
309309
}
310310
</script>
311311

312+
However, on the client side (i.e. in JavaScript's ``EventSource``), there is no built-in way
313+
to see which topic a certain message is coming from. So if this (or any other meta information)
314+
is important to you, you need to include it in the message's data (e.g. by adding a key to the
315+
JSON, or a `data-*` attribute to the HTML).
316+
312317
.. tip::
313318

314319
Test if a URI Template matches a URL using `the online debugger`_

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.