Skip to content

Add ability to get to Starscream's underlying SOCKS proxy property.#1108

Merged
designatednerd merged 1 commit intomasterfrom
add/websocket-property
Mar 31, 2020
Merged

Add ability to get to Starscream's underlying SOCKS proxy property.#1108
designatednerd merged 1 commit intomasterfrom
add/websocket-property

Conversation

@designatednerd
Copy link
Copy Markdown
Contributor

Addresses #1104. Definitely glad I went this way - it's not just that you have to set it on the web socket, you have to set it on the underlying stream. Ouch.

Anyway that's all abstracted away now so yay.

@designatednerd
Copy link
Copy Markdown
Contributor Author

@KonstantinEfimenko Wanna take a look?

return socket.enableSOCKSProxy
}
set {
guard var socket = self.websocket as? SOCKSProxyable else {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this has to be guard var as guard let wouldn't let me change enableSOCKSProxy since this protocol is not class-bound.

@KonstantinEfimenko
Copy link
Copy Markdown

Looks good. Thank you!

@designatednerd designatednerd merged commit 9a1ecc0 into master Mar 31, 2020
@designatednerd designatednerd deleted the add/websocket-property branch March 31, 2020 17:09
@designatednerd designatednerd added this to the 0.25.0 milestone Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants