v2.13.27

[danharrin]

What's Changed

• CHG: Make filament app.js defer by @bernhardh in CHG: Make filament app.js defer #3102
• create slug based on path and model class to prevent duplicate slugs by @mvenghaus in create slug based on path and model class to prevent duplicate slugs #2927
• Update turkish translations by @deligoez in Update turkish translations #3131
• Use Laravel Pint for code style by @zepfietje in Use Laravel Pint for code style #3126
• FIX: Respect action align setting by @bernhardh in FIX: Respect action align setting #2952
• Normalize English actions translations by @zepfietje in Normalize English actions translations #2885
• Feature: allow storing filters in session by @ralphjsmit in Feature: allow storing filters in session #2965
• Add enableOpen to FileUpload field by @pxlrbt in Add enableOpen to FileUpload field #2986
• Add Dusk selectors to actions and notification by @tanthammar in Add Dusk selectors to actions and notification #3021

New Contributors

• @mvenghaus made their first contribution in create slug based on path and model class to prevent duplicate slugs #2927
• @deligoez made their first contribution in Update turkish translations #3131

Full Changelog: v2.13.26...v2.13.27

---

This discussion was created from the release v2.13.27.

[xiaomlove]

In this version, Resource::getSlug() has made a big change, whether to use plural or not is related to locale, so how can I set locale dynamically?

The route is registered when the Service is started, and getSlug() uses the locale in config/app.php, which is en, and returns the plural(locale_has_pluralization() will get true in en). I change the locale in the middleware, for example to zh_CN, so that when rendering the backend menu, getSlug() does not return the plural(because locale_has_pluralization() will return false in zh_CN), resulting in an error occurred that the route is not defined.

What solution should I use to change the locale before registering the Resource route? I need to dynamically modify the locale based on the authenticated user information, or at least the cookie.

[danharrin]

We fixed this in a release today, could you check again?

[xiaomlove]

We fixed this in a release today, could you check again?

Good job, it's OK now, thanks!