feat: configurable auto slug pluralization in the database

[AlessioGr]

Fixes #2957

Description

• I have read and understand the CONTRIBUTING.md document in this repository

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have added tests that prove my fix is effective or that my feature works
• Existing test suite passes locally with my changes
• I have made corresponding changes to the documentation

[richadr]

• Instead of the general config, maybe it is a better idea to add this to collection config, and add an option there to control the underlying database collection/table name (allowing any name, rather than setting pluralization).
• Also, should this not come with changes to the documentation?

[AlessioGr]

• Also, should this not come with changes to the documentation?

You're totally right, I've added those!

Instead of the general config, maybe it is a better idea to add this to collection config, and add an option there to control the underlying database collection/table name (allowing any name, rather than setting pluralization).

So by setting pluralization to false, it should take exactly what you've provided as a slug for the document name in the database. The reason I set it as a global option is because I didn't really see a use-case for making it a per-collection setting. Why would someone want to disable it for some collections, but enable it for others? They might as well just set it to disabled globally and manually use pluralized slugs for collections where they want it to be enabled.

One thing I'm hoping to do anyways (not decided yet!) is disabling pluralization by default globally in v2.0 as well. Just makes no sense to have that in the first place, in my opinion, it's confusing if the data is saved differently than what's specified in the slug. Pretty unexpected behavior.

[DanRibbens]

• Instead of the general config, maybe it is a better idea to add this to collection config, and add an option there to control the underlying database collection/table name (allowing any name, rather than setting pluralization).

I agree with this. I would rather see a collection name property that overrides the default slug-derived naming instead of a global setting that modifies how collections are named.

[DanRibbens]

pluralizeSlugs we use "slug" for routing, not just mongoose collection naming. I don't think this property is the right approach.

[AlessioGr]

Closed in favor of #3153