Update axum from 0.7 to 0.8 version (breaking)
#1304
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: eternal-flame-AD <[email protected]>
tyranron
added
enhancement
tyranron
added
duplicate
Member
|
Duplicate of #1303 |
Member
|
@eternal-flame-AD released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for the project!
Axum just released 0.8 and changed a couple of things, and I tried upgrading and there are a couple places in
juniper_axumthat need changing (the type of WS message and remove::async_trait). This will be a breaking change to your user as the type for ["extract::ws::WebSocket"] is incompatible.