Fix async/sync view handling for mixed HTTP methods #1466
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.
Fixes #1347
Fix async/sync view handling for mixed HTTP methods
Fixes a bug where routes with mixed async/sync operations were incorrectly treating all operations as async. The fix:
is_async
flag fromPathView
that was causing this behaviorThis ensures sync operations (like POST/DELETE/PUT) are properly handled when sharing a path with async operations (like GET), resolving the
RuntimeWarning: coroutine was never awaited
error.This change was produced by Harry Patcher 🧙♂️, an autonomous & anonymous AI engineering agent. No human was involved in creating this pull request.
Learn more about Harry Patcher and how he came up with this fix here 🔍.
Harry cannot yet respond to review feedback. If the patch isn’t relevant, reject the PR and optionally let us know 📬.