Not getting ActionCable connected() when using litecable adapter

[westonganger]

In development when I switch to adapter: litecable in config/cable.yml then it is not calling the connected() function. It does successfully call the initialized() function.

Everything works correctly when I switch back to adapter: async where I get connected() and received()

I am using puma gem for development server on Rails 7.1. Let me know if there is any other information that would be helpful.

[adrienpoly]

I think I had a similar issue but this should be fixed on master by #41

[westonganger]

Yup switch to the master branch fixes this. Maybe we could have a new version released that has a functioning LiteCable implementation.

[westonganger]

Also would be really helpful to add a changelog entry stating this fix.

[westonganger]

@adrienpoly I see that you were trying to add a spec for this regression in another project rubyevents/rubyevents#50

Would be awesome if maybe we could get a spec for this inside the litestack repo itself.

[adrienpoly]

For sure yes I wanted to build a dummy app to add to the project but clearly running out of time right now. I f you can propose something that would be great for sure

[westonganger]

Yeah sure, I have the dummy app setup in all my other gems, so I can whip up a PR to get something going.

[westonganger]

Added some PRs to resolve a few of these items

• Add changelog entry for litecable connected fix #61
• Add dummy Rails app test suite and add Github CI workflow #62

[oldmoe]

I am planning a new release soon that will include all the pending fixes/improvements, just checking what else I can sneak in