Support setting client protocols after initialization #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm using this gem for some websocket tests in the Mastodon codebase, where we have support for authentication by abusing websocket subprotocols. Currently it's only possible to set the protocols when you initialize the WebSocket client, but not afterwards before starting the client, this means you have to know the protocols value immediately, not lazily.
This change to add support for setting the protocols after initialization but before start ended up being a bit gnarly, due to the way the headers worked.
I had to split the
set_header
headers from the@headers
because the tests all failed due to expecting headers in a specific line order, which became messed up otherwise