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

Move axum-handle-error-extract into axum #534

Merged
merged 3 commits into from
Nov 17, 2021

Conversation

davidpdrsn
Copy link
Member

With 0.4 underway we can now nuke axum-handle-error-extract and move
its code directly into axum.

So this replaces the old HandleErrorLayer with one that supports async
functions and extractors.

With 0.4 underway we can now nuke `axum-handle-error-extract` and move
its code directly into axum.

So this replaces the old `HandleErrorLayer` with one that supports async
functions and extractors.
@davidpdrsn davidpdrsn added this to the 0.4 milestone Nov 17, 2021
$name!(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15);
$name!(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16);
};
}
Copy link
Member Author

Choose a reason for hiding this comment

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

Probably the best macro 🙃

@davidpdrsn davidpdrsn enabled auto-merge (squash) November 17, 2021 19:05
@davidpdrsn davidpdrsn merged commit 9a41037 into main Nov 17, 2021
@davidpdrsn davidpdrsn deleted the nuke-axum-handle-error-extract branch November 17, 2021 19:10
EdorianDark pushed a commit to EdorianDark/axum that referenced this pull request Nov 24, 2021
* Move `axum-handle-error-extract` into axum

With 0.4 underway we can now nuke `axum-handle-error-extract` and move
its code directly into axum.

So this replaces the old `HandleErrorLayer` with one that supports async
functions and extractors.

* changelog

* fix CI
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.

None yet

2 participants