Michaelangelo Jong
Michaelangelo Jong
The issue here is **not** when `instance = {key: undefined}` but when `instance = undefined`. If `instance` is not a valid JSON type it should be invalid.
Yes there is a big difference and in my case I can't use `{ required: true }`. Example: ```js const schema = { type: 'object', required: [ 'a', 'b' ],...
That seems fair, and the work arounds work fine. I just found it non-intuitive (felt like a bug), but I guess its just how it was designed. Thanks for taking...
@0x777 Perfect that worked Thanks!
This would be helpful for excluding certain types in a generic type `T`. For example `Optional` doesn't really make sense so it would be nice if we could tell TypeScript...
While I do understand where those name come from they are still poor. The DOM API itself added additional methods for doing the same thing with the more intuitive names...
Since decorators require two arguments `@ ` we can determine that an `@` that receives no arguments that follows a `|>` can be treated as an injection point instead of...