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

MatchedPathWithFallbackFn behaves differently than expected #72

Open
Ptrskay3 opened this issue Oct 10, 2024 · 0 comments
Open

MatchedPathWithFallbackFn behaves differently than expected #72

Ptrskay3 opened this issue Oct 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Ptrskay3
Copy link
Owner

Ptrskay3 commented Oct 10, 2024

Context: #69 (comment)

This particular endpoint uses the MatchedPath extrator in axum, and if that fails then a fallback function is called instead. Maybe it is not a bug, but rather axum changed the behaviour the MatchedPath extractor, and this enum variant may be obsolete.

@Ptrskay3 Ptrskay3 added the bug Something isn't working label Oct 10, 2024
@Ptrskay3 Ptrskay3 mentioned this issue Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant