You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ActionCable.server in Channel instances is a code smell. It makes testing more difficult than it should be (parallel tests might have more than one server).
I'd even prefer to have just broadcast within the channel, not even server.broadcast, but we already have broadcast_to that has a slightly different logic (prepend stream names with the channel class name).
Given current design and compatibility with the previous version, probably, having connection.broadcast(...) is the way to go.
ActionCable.server
inChannel
instances is a code smell. It makes testing more difficult than it should be (parallel tests might have more than one server).I think
Connection
should exposeserver
, e.g.I don't think we should encourage users to write
ActionCable.server
except as a last resort.The text was updated successfully, but these errors were encountered: