#Custom Pipe can't resolve dependency of String

1 messages · Page 1 of 1 (latest)

daring frigate
#

nest don't know what would be the value of errorMessage

#

you could use new ParseObjectIdPipe() instead of relying on the DI system

#

another way is by marking that errorMessage parameter as optional like this:

constructor(@Optional() private errorMessage?: string) {}
north smelt
#

Ok, now it works, strange