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

Remove axum-test dependency #1270

Merged
merged 1 commit into from
Jan 2, 2025
Merged

Conversation

Turbo87
Copy link
Contributor

@Turbo87 Turbo87 commented Jan 1, 2025

The axum-test crate has not yet been updated to work with axum v0.8 and is blocking us from releasing support for it ourselves. Since we use very little functionality from it, we can just replace it with direct calls to the ServiceExt trait of tower.

This should unblock #1269

The `axum-test` crate has not yet been updated to work with axum v0.8 and is blocking us from releasing support for it ourselves. Since we use very little functionality from it, we can just replace it with direct calls to the `ServiceExt` trait of `tower`.
Copy link
Owner

@juhaku juhaku left a comment

Choose a reason for hiding this comment

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

Great, 🥇 Thanks for the patch

Copy link
Owner

@juhaku juhaku left a comment

Choose a reason for hiding this comment

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

Perhaps this could also be mentioned in CHANGELOG.md as well, 🤔

@Turbo87
Copy link
Contributor Author

Turbo87 commented Jan 2, 2025

it's only used internally though, so not sure how useful it is for users of the library to know 😅

@juhaku
Copy link
Owner

juhaku commented Jan 2, 2025

Yup, valid point, wondering the same, it does not change how the lib is used in anyways, and if they want to see they have access to full changelog anyway from the release, so they can find it, it is just bit more effort.

@juhaku juhaku merged commit 1d71a24 into juhaku:master Jan 2, 2025
12 checks passed
@juhaku
Copy link
Owner

juhaku commented Jan 2, 2025

Of we go with the merge. 😄

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