Kamil Mysliwiec
Kamil Mysliwiec
Well, so this one is problematic. The default, built-in exception filter automatically converts all errors to a JSON-compatible format (to respond with the "Internal server error" in case it received...
Sounds great! Do you have any further ideas regarding this feature request? if so, feel free to share them, I'd love to get familiar with the community expectations. 🔥
I'm pretty sure that you started to work on such integration already @weeco, correct? :)
Looking forward to it! If you have something to show already, let me know :)
> I can provide the Nest team access to the project for reviewing it if you think that it might be usable for you. That would be great @SqueezeToyAliens!
For anyone looking for a workaround - you can simply override the module class and provide a different `configure()` method
Is there any reason you can't inject & use the `Response` object? cc @SwinX >But whenever the DTO throws an error, it just sends it's default 400 : Bad Request...
> this makes user to handle the response explicitly. This may be not so trivial. Still, Isn't it more trivial than returning an object that must match a specific shape...
> Instead of a specific field view we may introduce some kind of ViewModel class, which instance may be returned from the controller handler. So we will not have to...