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 e5e62c4

Browse filesBrowse files
committed
Minor tweaks
1 parent 33dee6f commit e5e62c4
Copy full SHA for e5e62c4

File tree

Expand file treeCollapse file tree

1 file changed

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

1 file changed

+5
-4
lines changed

‎mercure.rst

Copy file name to clipboardExpand all lines: mercure.rst
+5-4Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -309,10 +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).
312+
However, on the client side (i.e. in JavaScript's ``EventSource``), there is no
313+
built-in way to know which topic a certain message originates from. If this (or
314+
any other meta information) is important to you, you need to include it in the
315+
message's data (e.g. by adding a key to the JSON, or a ``data-*`` attribute to
316+
the HTML).
316317

317318
.. tip::
318319

0 commit comments

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