Typescript generic schema usage

Do you want to request a feature or report a bug? BUG

What is the current behavior? Typescript isn’t shouting on missing properties, but it does shouting on extra properties or different naming properties.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior? Typescript isn’t shouting on missing properties, but it does shouting on extra properties or different naming properties. For example, in the above code, property b is missing in the schema, everything seems to work. (typescript compiled without errros)

What are the versions of Node.js, Mongoose and MongoDB you are using? Note that “latest” is not a version.

• Node LTS (14.17)
• Mongo 4.3
• Mongoose 6.0.4

[vkarpov15]

@GalDayan you can work around this by using a separate type definition for the schema definition object as shown below.

import { Schema, SchemaDefinition, Model, model } from 'mongoose';
  
interface IContract {
  a: string;
  b: string;
}

// Below will fail to compile if `a` or `b` are omitted
// error TS2741: Property 'b' is missing in type '{ a: StringConstructor; }' but required in type 'Required<{ a?: SchemaDefinitionProperty<string>; b?: SchemaDefinitionProperty<string>; }>'
const schemaDef: Required<SchemaDefinition<IContract>> = { a: String, b: String };

const schema = new Schema<IContract>(schemaDef);

[GalDayan]

Got ya. Is there any option to make it required and not partial? @vkarpov15