This repository was archived by the owner on Dec 12, 2021. It is now read-only.
Open
Conversation
|
this gem is not supported. Please look on https://github.com/dotpromo/danthes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I doubt that this will be merged anytime soon into master, but this code allows clients to publish messages directly. Before, you always had to call some rails code in order to publish messages in non-meta channels.
However, the contents published this way are not sanitized in any way or form. This should either be done by the receiving client or the faye server itself.
To control which channels a client may publish to you can specify the option
publish(default: false) when callingsubscribe_to: