fix(content-manager): return default locale

[yurimutti]

What does it do?

Added key on InjectionZone to reset internal states.

Now with params.locale as key. Default locale can be persisted after user click on collection.

Why is it needed?

Locale filter doesn't have correct locale loaded when user click on collection type again.

How to test it?

• npx create-strapi-app@latest my-project --quickstart
• log into Strapi V4
• Select Resources collection from Content Manager
• on the right hand side top of the resource table/ index, select a locale from the locale drop down
• then click Resources collection on the left nav list

Related issue(s)/PR(s)

Fix #20209

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
contributor-docs	❌ Failed (Inspect)			May 3, 2024 10:12am

[yurimutti]

[joshuaellis]

Can you rebase off develop please, your PR should not have this many commits.

Also I'm not sure this is the appropriate solution, I think we should be looking at how the injected component works in i18n rather than trying to solve it in the CM.

This also assumes i18n is installed and adds locale which isn't necessary true and pollutes the CM domain with i18n concepts, something we try to avoid where possible.

[yurimutti]

Can you rebase off develop please, your PR should not have this many commits.

Also I'm not sure this is the appropriate solution, I think we should be looking at how the injected component works in i18n rather than trying to solve it in the CM.

This also assumes i18n is installed and adds locale which isn't necessary true and pollutes the CM domain with i18n concepts, something we try to avoid where possible.

Yes, one agnostic solution works in i18n makes total sense.