Edward Mackenzie
Edward Mackenzie
Reposting issue from invserify-express-utils here. https://github.com/inversify/inversify-express-utils/issues/378 ## Expected Behavior When using the BaseHttpController helper method BaseHttpController.json(...) the resulting express call coerces the json object to a string. This causes problems...
Using zod's type inference (schema first approach) I get typescript errors when using catchall. Example: ```typescript import z from 'zod'; const zschema = z .object({ 'main': z.string() }) .catchall(z.number().optional()); const...
When using the `BaseHttpController` helper method `BaseHttpController.json(...)` the resulting express call coerces the json object to a string. This causes problems when using express middleware that validates JSON responses (in...
I'm currently working on a project with a lot of tests. Currently they are all collected together and run via Jasmine, however I'm looking to break them out into separate...
**Describe the bug** Given a rule that defines a nested field should not exist (i.e. `$exists: false`) it behaves as expected if all nesting up to the relevant field is...
The `lib/esm/static.d.ts` file in the (currently) latest version (`1.0.0-rc.12`) defines: ```typescript import type { CheerioAPI, Cheerio } from '.'; ``` This causes ESM projects that use cheerio to fail to...
## Describe the bug\* When serializing a complex object with defined relationships, all related fields are included in the attributes by default as well as in relationships. To avoid this,...
Reposting issue from invserify-express-utils here. https://github.com/inversify/inversify-express-utils/issues/378 ## Expected Behavior When using the BaseHttpController helper method BaseHttpController.json(...) the resulting express call coerces the json object to a string. This causes problems...