#Using an exception filter that was defined in another package

5 messages · Page 1 of 1 (latest)

strong hatch
#

Howdy, we are currently building several services that are based on a single shared package

I'm finding that when I define an exception filter in the shared package, and import it to use within a controller in an API built including the package - the error is not caught by the filter
However, if I copy the exception filter over to the API and use that version, it works as expected, and the error is caught in the filter

Is there any particular reason the imported filter might not work?

versed sierra
#

Does the package use dependencies or peer deps for the nest packages?

strong hatch
#

Looks like it's a dependency

versed sierra
#

That's an issue

strong hatch
#

Thanks, I'll poke around with that a bit