From 484b3ca4023c04fa31c7dc8c3de4dcd428d6e63b Mon Sep 17 00:00:00 2001 From: Prathamesh Sonpatki Date: Fri, 12 Aug 2016 12:19:34 +0800 Subject: Fix remaining broadcasting_name example from Action Cable guide [ci skip] - Followup of https://github.com/rails/rails/pull/26125. --- guides/source/action_cable_overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'guides/source/action_cable_overview.md') diff --git a/guides/source/action_cable_overview.md b/guides/source/action_cable_overview.md index 02db86888c..c9c2b550d5 100644 --- a/guides/source/action_cable_overview.md +++ b/guides/source/action_cable_overview.md @@ -510,10 +510,10 @@ WebNotificationsChannel.broadcast_to( The `WebNotificationsChannel.broadcast_to` call places a message in the current subscription adapter's pubsub queue under a separate broadcasting name for each user. For a user with an ID of 1, the broadcasting name would be -"web_notifications_1". +`web_notifications:1`. The channel has been instructed to stream everything that arrives at -"web_notifications_1" directly to the client by invoking the `received` +`web_notifications:1` directly to the client by invoking the `received` callback. The data passed as argument is the hash sent as the second parameter to the server-side broadcast call, JSON encoded for the trip across the wire, and unpacked for the data argument arriving to `received`. -- cgit v1.2.3