[lazerg]

Summary

Fix #16564

Schema.Types.Int32 casts to a plain JS number at runtime, but NumberSchemaDefinition didn't include it. So a Schema<{ priority: number }> rejected type: Schema.Types.Int32, and inference fell through to the typeof SchemaType branch and typed the path as a Schema.Types.Int32 instance. This adds Schema.Types.Int32 (and the 'int32'/'Int32' strings, which mongoose also accepts) to NumberSchemaDefinition, so those paths are typed as number everywhere number paths are.

Examples

const schema = new Schema({ priority: { type: Schema.Types.Int32, required: true } });
const doc = new (model('Test', schema))({ priority: 1 });
const priority: number = doc.priority; // was TS2322, now compiles

[Copilot]

Copilot review overview

🟢 Approval recommended

The implementation is correct, with only minor missing coverage for the lowercase alias.

Review effort: Balanced
Findings: 1

Open (1)

• Add coverage for lowercase int32 alias inference · New

What changed in this PR

Updates Int32 schema definitions so TypeScript consistently treats Int32 paths as JavaScript numbers.

Changes:

• Adds Int32 constructors, instances, and string aliases to NumberSchemaDefinition.
• Adds compile-time coverage for typed, inferred, lean, and raw documents.

File	Description
types/​index.d.ts	Classifies Int32 schema definitions as numeric.
test/​types/​schema.test.ts	Verifies Int32 type inference.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[vkarpov15]

Thanks 👍