Open
Conversation
leastbad
added
enhancement
Contributor
Author
|
We haven't discussed this one, so I won't feel bad if you don't pick it up. I just figured that I'd strike while the memory was hot. Also: please delete the |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Type of PR (feature, enhancement, bug fix, etc.)
Enhancement
Description
Action Cable messaging queue based on similar functionality to what was recently added to StimulusReflex.
Allows transmission or queueing of events - both individual and batch - based on the connection status of the AC subscription.
Why should this be added
Shrinks codebase size and complexity without reimplementing a falloff mechanism. Instead of retries, why not wait until Action Cable is ready for us to send?
Checklist