| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
address code review comments | 6 个月前 | |
additional clarification and test coverage for #11528 in light of #9232 | 1 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
docs: fix code review comment | 3 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
perf: omit cloned properties with object rest | 1 个月前 | |
fix(schema): clone a document array element with its own constructor signature Fixes #16462 | 1 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
fix(schema/index): expose "DocumentArrayElement" | 8 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 | |
fix: address PR feedback | 6 个月前 | |
fix(schema): put enum on array elements and support the object enum form in toJSONSchema `toJSONSchema()` read enum values straight off `schemaType.options.enum`, the raw user input. For an array of enums that put the `enum` keyword on the array rather than on its items, so the generated $jsonSchema rejected every document Mongoose considered valid. The documented `{ values, message }` form threw a TypeError when spread, and an enum declared on the array element or set with `.enum()` was dropped entirely. Emit the enum from the schema type that owns it, using the normalized `enumValues`, so arrays describe their items and every enum declaration form is covered. Fix #16443 | 1 个月前 | |
feat(schema): include ObjectId regex pattern in toJSONSchema output re #16334 | 3 个月前 | |
fix(schema): put enum on array elements and support the object enum form in toJSONSchema `toJSONSchema()` read enum values straight off `schemaType.options.enum`, the raw user input. For an array of enums that put the `enum` keyword on the array rather than on its items, so the generated $jsonSchema rejected every document Mongoose considered valid. The documented `{ values, message }` form threw a TypeError when spread, and an enum declared on the array element or set with `.enum()` was dropped entirely. Emit the enum from the schema type that owns it, using the normalized `enumValues`, so arrays describe their items and every enum declaration form is covered. Fix #16443 | 1 个月前 | |
perf: omit cloned properties with object rest | 1 个月前 | |
style: apply "eol-last" rule | 4 年前 | |
fix(schema): remove validateSync union fallback re #16291 | 3 个月前 | |
refactor: move createJSONSchemaTypeDefinition into schematype method for _id logic | 5 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 6 个月前 | ||
| 1 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 3 个月前 | ||
| 5 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 5 个月前 | ||
| 8 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 6 个月前 | ||
| 1 个月前 | ||
| 3 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 4 年前 | ||
| 3 个月前 | ||
| 5 个月前 |