Remove schema reserved words

[j]

There has to be a way to not have any reserved words. I'm working with existing data which has "options" as a key. Welp, that happens to be a reserved key in schemas and throws an error for me. Granted, I can probably map this some other way, or if mongoose allowed for field name mapping (which is a separate issue), I feel that the use of the word "option" or "options" is a common word.

Anyway, what do you think?

[j]

After googling, this seems to be an issue for a lot of people, but i feel that it's a quick hacky fix to just throw an error and not allow certain properties.

Users should be able to use things like, "model" or "collection", or "options" if they would like I think. There has to be a way to separate field mapping from schema reserved properties/methods.

[aheckmann]

Definitely. Needs to wait for v4 though due to user interface impacts.

[j]

Sweet, I'm starting to understand the core, so I'll try to knock out some issues on my free time to help you out.

[aheckmann]

Awesome!

[hasezoey]

This issue is basically a duplicate (of the later) #9010, which was fixed by #10414, which was released in 6.0.0 (or 6.0.0-rc2).

The mentioned PR "only" changed that the reserved keywords are not a error anymore, but a warning, but should still resolve this issue.

I think this can be closed @vkarpov15 , @IslandRhythms @Uzlopak

PS: this issue should also maybe be added to the correct milestone, if closed