moleculer-zod-validator - npm Package Versions

Added the .return property to ZodParams. This is a utility to store return types that can be used for typing action calls elsewhere.

Return values are provided by providing a type on a new third optional constructor parameter. It does not matter what is passed in, so long as it is given the desired return types using the as keyword. Once stored, these can be referred to in the same way that you would access .call and .context.

const sampleParam = new ZodParams({ property: z.string() }, undefined, {} as Promise<string>);

... 

const returnedValue = broker.call<typeof sampleParam.return, typeof sampleParam.call>({ property: "whatever" });
// type of returnedValue is Promise<string>

Updated dev dependencies

Type inference now works (mostly) as expected! While the runtime behavior of the package worked as expected during work on 3.0.0 and was what I had been testing, I somehow was completely unaware that type inference was completely broken. It's a bit embarrassing for me, to be honest. It took more energy than I had anticipated to make it work, but type inferences now behave when using typeof .call and typeof .context almost exactly as they do in Zod with z.input<typeof validator> and z.infer<typeof validator>/z.output<typeof validator>. This closes Issue #5.

I do say almost, as there is an important note that is worth mentioning. There's a known upstream bug in Zod where using .catchall() results in bugged TypeScript type inference. While I could have left that behavior in ZodParams for parity with Zod, the sudden introduction of that behavior could break builds (it already broke one of our tests, through no fault of my own), so for the time being I've disabled catchall type inference in ZodParams. When the bug is fixed upstream, I'll reenable that behavior here.

Beyond all of this, there should be no other changes and everything should Just Work™ as expected.

Updated dev dependencies

• BREAKING CHANGE - Removed the compiledValidatorOnly nested options object. The two settings, strip and passthrough, are now present in the top level options object.
• BREAKING CHANGE - The default validation mode is now strip as opposed to passthrough.