params don't seem to be parsed out of connection requests

[nathan-eko]

If I mount my ActionCable app as such:

mount ActionCable.server => "/socket(/:channel/:resource_id)"

My connection objects receive and have access to request.params[:channel] and request.params[:resource_id] much as I would expect.

If I then write a test to verify the behavior of my Connection class' authentication logic

expect { connect "/socket/somechannel/somebogusid" }.to have_rejected_connection

My Connection class receives empty params in the Request object. This basically means I cannot test anything I need to.

Am I missing something or is this a legitimate deficiency of this library?

[palkan]

You can use params: ... like in controller tests:

expect { connect params: {channel: "somechannel", resource_id: "somebogusid"} }.to have_rejected_connection

If I mount my ActionCable app as such:
mount ActionCable.server => "/socket(/:channel/:resource_id)"

That's an interesting example (haven't thought about it, tbh); beware, that it relies on Rails router to populate the params and won't work if you decide to run Action Cable in a standalone mode.