The only difference between the HTTP exception filter layer and the corresponding microservices layer is that instead of throwing
HttpException, you should use
info Hint The
RpcExceptionclass is imported from the
With the sample above, Nest will handle the thrown exception and return the
error object with the following structure:
Microservice exception filters behave similarly to HTTP exception filters, with one small difference. The
catch() method must return an
warning Warning You cannot set up global microservice exception filters when using a hybrid application.
The following example uses a manually instantiated method-scoped filter. Just as with HTTP based applications, you can also use controller-scoped filters (i.e., prefix the controller class with a
Typically, you'll create fully customized exception filters crafted to fulfill your application requirements. However, there might be use-cases when you would like to simply extend the core exception filter, and override the behavior based on certain factors.
In order to delegate exception processing to the base filter, you need to extend
BaseExceptionFilter and call the inherited
The above implementation is just a shell demonstrating the approach. Your implementation of the extended exception filter would include your tailored business logic (e.g., handling various conditions).