You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm facing a situation that I do not know if it is a bug or my mistake...
In a repository I throw a new exception in order to control configurations issues in the API. When I do this, a Try/Catch in the resolver catches the exception and, at that moment, I throw that exception (without the new keyword, subbmitting it to a higher level). The ackward situation is that the Exception Midleware do not capture it and the execution returns to the point the exception was initially thrown.
Is this correct? Or I'm doing anything wrong?
Tks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I'm facing a situation that I do not know if it is a bug or my mistake...
In a repository I throw a new exception in order to control configurations issues in the API. When I do this, a Try/Catch in the resolver catches the exception and, at that moment, I throw that exception (without the new keyword, subbmitting it to a higher level). The ackward situation is that the Exception Midleware do not capture it and the execution returns to the point the exception was initially thrown.
Is this correct? Or I'm doing anything wrong?
Tks!
Beta Was this translation helpful? Give feedback.
All reactions