MongooseModule: same schema multiple collections

[silvelo]

I'm submitting a...

[ ] Regression 
[ x] Bug report
[x ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

In Mongo for the same schema
TypeSchema
name: string
_id: ObjectID

is used by multiple collections:
CategoriesCollection
TypesCollection

When you use the mongooseModule, you can define well this collections, but when you inject them on service with @InjectModel(TypeSchema), only one Model is reference.

This is because you inject it with schema as parameters, injectModel as name collections will be better to avoid this.

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Use the same schema for multiple collections.

Environment

Nest version: 4.5.9

 
For Tooling issues:
- Node version: v8.9.4
- Platform:  Windows

Others:

[silvelo]

I was looking in the code, and found the provide is a JSON.stringify of Schema model, for that is you use the same schema even with differents names this problem appear.

I go change the code and make a PR soon with "fix"

[silvelo]

@kamilmysliwiec, Can you check this?

[BorntraegerMarc]

Is there an update on this?

[silvelo]

Only @kamilmysliwiec can do merge, so need wait. Meanwhile I compile with tsc the PR and replace the @nest/mongoose folder to use because in my project I need it.

[kamilmysliwiec]

Hey, will try to verify this today.