-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make url as feature and bump version #419
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. One question though: why is the newly introduced tests/url_feature.rs
is a copy-paste of the existing test (with the only single exception of using Url
)? - I think this might be a bit confusing.
Yes. Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Just to clarify one thing: if I got your intentions right, you want us to publish a new version after merging this PR, right? (otherwise CHANGELOG should contain Unreleased
instead of 0.22.0
and also the update in the Cargo.toml
would also not be necessary).
AFAIR originally we wanted to first wait for #363 first and then release a version. But if a builder pattern is useful on its own, we could make a release before #363 I think.
Co-authored-by: Daniel Abramov <[email protected]>
Co-authored-by: Daniel Abramov <[email protected]>
Yes, make a release version is my goal. With a new version I could (update and) merge rerun-io/ewebsock#27 crate which is using tungstenite For #363 I think @conorbros is a little busy at the moment because I sent him a PR (shotover#1) but he didn't accept it for now A solution could be to merge https://github.com/Its-Just-Nans/tungstenite-rs/tree/master directly into tungstenite (without passing by the fork of @conorbros). But that would make @conorbros invalid his PR. I don't know if it's a good and acceptable way of doing it Thanks for the suggested modifications! |
I think #363 may be mergeable now (thank you @conorbros) ! So maybe we can merge #363 then this one ? |
That makes sense. I think we could merge #363; it just requires minor updates to pass the CI. |
@daniel-abramov I think this PR is blocked by invisible/old "requested changes" |
Hello,
This PR fixes:
url
crate in the next version. #412