Feature/60 use same collection with different patterns

[TMSchipper]

What does it do?

Describe the technical changes you did.

Why is it needed?

Describe the issue you are solving.

How to test it?

Provide information about the environment and the path to verify the behaviour.

Related issue(s)/PR(s)

Let us know if this is related to any issue/pull request

[changeset-bot]

⚠️ No Changeset found

Latest commit: a187578

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[boazpoolman]

Hi @TMSchipper
This looks really good, nice work.

I've left a couple comments regarding code style and some potentially unhandled bugs.

I also think you need to address the following things before we can get this merged:

1. The host entity will still have a relation to only a single url_alias. We should probably update that to be a oneToMany relation instead of oneToOne. So then the entity will actually have a relation to all it's URL aliases.
2. When we've established the oneToMany relation we need to have a way to define what is the primary URL alias of an entity. This is the URL alias which will be used when we're linking from one page to another. We need to have a single URL alias to make that link.
3. We need to have a way for the Strapi Editor manage the multiple URL aliases. This needs to be developed in the admin panel. That way we can see the different URL aliases and manage them from within the edit form of a page.
4. We probably need to update/add some unit tests for this new feature.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.96%. Comparing base (c32aee9) to head (a187578).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #161      +/-   ##
==========================================
- Coverage   38.14%   37.96%   -0.18%     
==========================================
  Files           4        4              
  Lines         839      864      +25     
  Branches      181      189       +8     
==========================================
+ Hits          320      328       +8     
- Misses        419      432      +13     
- Partials      100      104       +4     

Flag	Coverage Δ
unit	37.96% <ø> (-0.18%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.