ActionCable Issue
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 32
- Forks
- 19
- Avg merge
- 19h 27m
- Merged PRs (30d)
- 1
Description
Something prevents ActionCable from working well with clerk-sdk-ruby gem.
This config worked for me as a temporary workaround. Otherwise, web socket connections fail without any errors in the logs. It's unclear how I would go about identifying users in WS connections without digging into gem's source code.
Clerk.configure do |c|
c.excluded_routes = ['/cable']
end
To test this you can simply create a blank new Rails 7 project with some turbo_frame_tag and a gem "clerk-sdk-ruby" and see that WS connections fail
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in a blank Rails 7 project using a turbo_frame_tag and the clerk-sdk-ruby gem, then test ActionCable connections with and without excluding /cable. Compare the behavior and determine what is needed for WebSocket connections to work and for users to be identified without requiring source-code investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100