Docs: Clarify forcing DOM update with authentication

[stimulusreflex]

Docs: Clarify forcing DOM update with authentication

[leastbad]

Hey @henrik! You should join the SR Discord. :)

I am just reading through this and what you posted on the forum. Will reply soon.

[henrik]

Hi @leastbad - thanks so much for the thoughtful reply.

Clever idea setting up the subscription inside the Stimulus controller to save a level of indirection. I’ll certainly borrow that :)

I’ll read up further on the two kinds of streaming and experiment. Will try to take the time to improve the Action Cable docs when I understand those better.

And I’ll jump in the Discord on my next lab day! Not for a few weeks, probably.

[leastbad]

It's possible that #25 (comment) will provide some insight.

What took me a while to figure out (poor ActionCable documentation) is that there's really two modes channels can operate in, stream_from and stream_for. Most people seem to think in terms of stream_from because it's the default that the generator creates. In some ways this is a shame because I actually find stream_for useful for all kinds of things.

Whereas stream_from is tied to a session id, stream_for is tied to a resource. For example, everyone looking at Post#29. If you want to send an individual User notifications, you can stream_for and broadcast to User#16.

Now, if you're trying to broadcast to everyone connected at the same time, you could probably figure out how to stream for a common object and have everyone subscribe to that object. For example, it might be possible to stream_for Rails, because why not? I haven't actually tried it. Let me know if it works!

[leastbad]

Just wanted to follow-up on this. Have you been able to revisit your project?

We are always looking to improve the documentation and lower the barrier to entry for those onboarding.

[henrik]

I'm afraid I haven't – Coronavirus wreaked havoc on our lab days. Might not happen for a while. Please feel free to close this ticket unless you plan on working on it independent of my efforts, and I can possibly revisit this later if and when I get back to it :)

[leastbad]

I hope that you and yours are well!

There’s no urgency to close anything. I was actually just checking in to see if I could be of service.

With OSS you do have to ask about issues that remain open, or else it starts to look like you’re not fixing problems with the library. Generally the Discord is actually the best way to get help.

[henrik]

Oh yeah, everyone's well, thankfully – just will affect priorities at work for a while. Hope you're well too.

Completely understand – you're doing a great job :)