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

fix(qe): Ensure middleware for FindXOrThrow captures exceptions #16433

Merged
merged 1 commit into from Nov 28, 2022

Conversation

miguelff
Copy link
Contributor

@miguelff miguelff commented Nov 24, 2022

Fixes #16354 (more precisely, it tests that the problem was fixed in #16162)

To be shipped after #16287. Once #16287 is merged, this has to be rebased again main, and the base branch changed.

@miguelff miguelff requested review from a team and millsp and removed request for a team November 24, 2022 12:12
@miguelff miguelff self-assigned this Nov 24, 2022
Base automatically changed from fix/error-logging to main November 25, 2022 11:54
@miguelff miguelff added this to the 4.7.0 milestone Nov 28, 2022
@miguelff miguelff merged commit 8509fbb into main Nov 28, 2022
@miguelff miguelff deleted the fix/error-logging-middleware branch November 28, 2022 08:57
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.

No way to catch error in findUniqueOrThrow via middleware
2 participants