Separates the linting from the tests so it becomes easier to see what is actually failing.
The bigger issue here is that Chrome was rejecting actioncable. What seems to be happening is that the subscription is not created before the websocket is open. So when we try to notify subscriptions there are no subscriptions to notify.
Once we have access to the action cable consumer (which should happen in this PR: https://github.com/hopsoft/stimulus_reflex/pull/444) would could possibly customize this behaviour in a better way so that when the websocket consumer is actually open we would could make sure that the flag on actioncableConsumer is appropriately flagged.
Checklist
[x] Tests are passing
[x] Documentation has been added or amended for this feature / update
Type of PR (feature, enhancement, bug fix, etc.)
Description
Separates the linting from the tests so it becomes easier to see what is actually failing.
The bigger issue here is that Chrome was rejecting actioncable. What seems to be happening is that the subscription is not created before the websocket is open. So when we try to notify subscriptions there are no subscriptions to notify.
Once we have access to the action cable consumer (which should happen in this PR: https://github.com/hopsoft/stimulus_reflex/pull/444) would could possibly customize this behaviour in a better way so that when the websocket consumer is actually open we would could make sure that the flag on
actioncableConsumeris appropriately flagged.Checklist