Pluralize metadata name for 1:1 relationship #9
Description
Is your feature request related to a problem? Please describe.
It is annoying to model a metadata for a 1:1 relationship with a syntactically incorrect name.
E.g. I have a category metadata for my portfolio projects. This is translated in the following route:
/projects/category/[slug]
but the correct one should be /projects/categories/[slug]
Describe the solution you'd like
pluralize metadata names
- category -> categories
- project -> projects
- ..
Describe alternatives you've considered
I can create a 1:1metadata directly with the plural form of its name but it is not the natural way of thinking.
Additional context
N/A