Skip to content
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

Merged
merged 5 commits into from
May 13, 2024
Merged

Conversation

Its-Just-Nans
Copy link
Contributor

Copy link
Member

@daniel-abramov daniel-abramov left a 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.

@Its-Just-Nans
Copy link
Contributor Author

Yes.
I changed the test. Is that better ?

Thanks

Copy link
Member

@daniel-abramov daniel-abramov left a 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.

CHANGELOG.md Outdated Show resolved Hide resolved
Cargo.toml Outdated Show resolved Hide resolved
Its-Just-Nans and others added 2 commits April 25, 2024 22:00
Co-authored-by: Daniel Abramov <[email protected]>
Co-authored-by: Daniel Abramov <[email protected]>
@Its-Just-Nans
Copy link
Contributor Author

Its-Just-Nans commented Apr 25, 2024

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.

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!

@Its-Just-Nans
Copy link
Contributor Author

I think #363 may be mergeable now (thank you @conorbros) !

So maybe we can merge #363 then this one ?

@daniel-abramov
Copy link
Member

That makes sense. I think we could merge #363; it just requires minor updates to pass the CI.

@Its-Just-Nans
Copy link
Contributor Author

Its-Just-Nans commented May 13, 2024

@daniel-abramov I think this PR is blocked by invisible/old "requested changes"

@daniel-abramov daniel-abramov merged commit c21281a into snapview:master May 13, 2024
6 checks passed
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