fix: allow defining path type option as an array

[mohamedjkr]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

When trying to declare an array schema path with additional options, an error is thrown due to invalid schema configuration.

import { Prop, Schema, SchemaFactory } from '@nestjs/mongoose';
import { Document } from 'mongoose';
    
class Profile extends Document {
  @Prop()
  name: string;
}

@Schema()
class Community extends Document {
  @Prop({ type: [Profile], required: true })
  profiles: Profile[];
}
export const communitySchema = SchemaFactory.createForClass(Community);

throws Invalid schema configuration: 'Profile' is not a valid type within the array 'profiles'.

The only way to fix it is by using @Prop({ type: [SchemaFactory.createForClass(Profile)], required: true }), or using @Prop([Profile]) while loosing the ability to pass additional options

Issue Number: #839

What is the new behavior?

The PR allows defining type option as an array of subdocuments so that @Prop({ type: [Profile], required: true }) would work as expected.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[kamilmysliwiec]

Can you please rebase so the workflows execute as expected?

[mohamedjkr]

@kamilmysliwiec Rebased 👍 Let me know if you need any further changes before approving!