TypeScript Bug: error when defining required array

[rattrayalex]

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

bug

What is the current behavior?

TypeScript Playground Link

import mongoose, { Model, Schema } from "mongoose"; // v5.13.8
export type Foo = {
  bar: string
  schedule: {
    date: string;
    hours: number;
  }[];
};

type FooModel = Model<Foo>;

const FooSchema = new Schema<Foo, FooModel, Foo>(
  {
    bar: { type: String },
    schedule: {
      type: [
        {
          date: { type: String, required: true },
          hours: { type: Number, required: true },
        },
      ],
      required: true,
    },
  }
)

Error:

        Type '{ date: { type: StringConstructor; required: true; }; hours: { type: NumberConstructor; required: true; }; }' is not assignable to type 'Schema<{ date: string; hours: number; }, Model<{ date: string; hours: number; }, any, any>, {}>'.
          Object literal may only specify known properties, and 'date' does not exist in type 'Schema<{ date: string; hours: number; }, Model<{ date: string; hours: number; }, any, any>, {}>'.

(easier to see on the TS playground link, above).

If I change my schema to this, it works fine:

    schedule: [
        {
          date: { type: String, required: true },
          hours: { type: Number, required: true },
        },
      ],

but of course, I want the schedule to be required!

What is the expected behavior?

No type error

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

{
"typescript": "^4.3.5",
"mongodb": "^3.5.7",
"mongoose": "5.13.8",
"@types/mongodb": "3.6.20"
}

[vkarpov15]

I can confirm this was fixed in v6.0.4 with #10605. We'll move this to our v5.13.10 milestone so we know to backport it when we have time, but I don't expect us to get to that for another week or two. Are you able to upgrade to Mongoose 6.x or is there something blocking you?

[rattrayalex]

Awesome thank you!

No known blockers, just general fear of breaking changes and upgrades (and frankly while the migration guide looks comprehensive, it's a little hard to quickly glean what issues we should mostly look out for). But we can definitely give it a try!