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

feat: moved connect module to legacy #49

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

kaffarell
Copy link
Contributor

Moved the connect module to the legacy namespace to make space for new changes. Renamed legacy.rs -> client.rs and also moved to that namespace.

Fixes: hyperium/hyper#3414

examples/client.rs Outdated Show resolved Hide resolved
@seanmonstar
Copy link
Member

Looks like the feature flags need to be adjusted.

Moved the `connect` module to the legacy namespace to make space for new
changes. Renamed legacy.rs -> client.rs and also moved to that
namespace.

Fixes: hyperium/hyper#3414
@seanmonstar seanmonstar merged commit de1ff4c into hyperium:master Nov 16, 2023
15 checks passed
howardjohn added a commit to howardjohn/hyper-util that referenced this pull request Nov 16, 2023
Since hyperium#49, we cannot refer to the Error response from the client. This
exposes it again
seanmonstar pushed a commit that referenced this pull request Nov 16, 2023
Since #49, we cannot refer to the Error response from the client. This
exposes it again
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.

hyper-util: move connect under legacy module?
2 participants