You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are somewhat overloading the "type" property to allow it to contain things like "date". I overload it myself for a MongoDB "ObjectId".
What if instead we just used {type:"object", instance:"ObjectId"}? This would be a little bit closer to ECMAScript semantics, without overloading JSON Schema semantics.
For cases where you want to say an object can't be an instance of anything, you only want it to be a key-value map, you could use {type:"object", instance:false} maybe.
The text was updated successfully, but these errors were encountered:
Right, {type:"date"} could continue to be supported, I don't think we'd even need to deprecate it; but in my usage it would raise as an invalid JSON Schema against the meta-schema.
Right now we are somewhat overloading the "type" property to allow it to contain things like "date". I overload it myself for a MongoDB "ObjectId".
What if instead we just used
{type:"object", instance:"ObjectId"}
? This would be a little bit closer to ECMAScript semantics, without overloading JSON Schema semantics.For cases where you want to say an object can't be an instance of anything, you only want it to be a key-value map, you could use
{type:"object", instance:false}
maybe.The text was updated successfully, but these errors were encountered: