Fix schema property type definition in SchemaType
#15631
Merged
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently, the
SchemaTypeproperty ofschemais required in the type definition and its JSDoc describes the property as "The schema this SchemaType instance is part of".Instead, based on how mongoose actually works, it should be optional and the JSDoc should be changed, since it's not actually the
Schemathat theSchemaTypeis part of. Instead, theschemaproperty only exists when theSchemaTypeis for a subdocument or document array and it refers to the actual subdocument schema itself.Examples
Here's an example showing how the
schemaproperty isn't present on every SchemaType, just to prove that the Typescript definition should be changed to optional and its JSDoc should be modified accordingly.