Skip to content

[Strapi 5️⃣] Document breaking change for i18n CM locale parameter#1991

Merged
pwizla merged 4 commits intov5/mvpfrom
v5/breaking-changes--i18n-moved-to-core
Feb 1, 2024
Merged

[Strapi 5️⃣] Document breaking change for i18n CM locale parameter#1991
pwizla merged 4 commits intov5/mvpfrom
v5/breaking-changes--i18n-moved-to-core

Conversation

@pwizla
Copy link
Collaborator

@pwizla pwizla commented Jan 29, 2024

plugins[i18n][locale]locale

@pwizla pwizla self-assigned this Jan 29, 2024
@vercel
Copy link

vercel bot commented Jan 29, 2024

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

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 1, 2024 3:27pm

@pwizla pwizla requested a review from Marc-Roig January 29, 2024 15:52
@pwizla pwizla added this to the 5.0.0-beta milestone Jan 29, 2024
@pwizla pwizla added source: Dev Docs PRs/issues targeting the Developer Docs v5 Documentation PR that targets Strapi v5 labels Jan 29, 2024
Comment on lines +26 to +36
**In Strapi v4**

Content Manager sends the following parameter when accessing a locale: `plugins[i18n][locale]`.

</SideBySideColumn>

<SideBySideColumn>

**In Strapi v5**

The parameter sent to the Content Manager is now just `locale`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this could be marked as an "internal" breaking change, as this is something not normally exposed to users.

This change is not really user-facing, but it could be important for folks who deeply customize strapi.

I would personally not put it at the same level as the other breaking changes.

The docs look good !

Copy link
Collaborator Author

@pwizla pwizla Jan 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see! The docs.strapi.io website is supposed to be only for user-facing things.

I'll add a mention to the docs page for now, and I'll keep it in mind and see if we have other breaking changes of this type. Do you think we should add a property to the Notion database to differentiate "internal" vs. "external" breaking changes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 Probably it could be great if there weren't many internal breaking changes, so maybe it's not worth mentioning this internal change.

I originally liked how react flow ( a react library) presents its breaking changes. They have a Internal changes section where they mention things like this.

But yeah.. If we do that we should be documenting everything that we are breaking internally, and that might be too much :/ So if docs.strpai.io is for user facing things, maybe I would exclude this point, and remove it from our notion db too.

Copy link
Collaborator Author

@pwizla pwizla Jan 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion, Marc! I'll keep the page for now and we'll see how things go over time :)

Copy link
Collaborator Author

@pwizla pwizla Jan 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've just pushed it to an "internal changes" section. Thank you for the recommendation, Marc, very good idea!
(see commit and live preview)

@pwizla pwizla merged commit df934e5 into v5/mvp Feb 1, 2024
@pwizla pwizla deleted the v5/breaking-changes--i18n-moved-to-core branch February 1, 2024 15:25
@pwizla pwizla modified the milestones: 5.0.0-beta, 5.0.0 (stable) Jun 12, 2024
@pwizla pwizla modified the milestones: 5.0.0 (stable), 5.0.0-rc.0 Jun 26, 2024
@pwizla pwizla modified the milestones: 5.0.0-rc.0, 5.0.0 (stable) Aug 13, 2024
@pwizla pwizla added the pr: new content PRs for new product features or new documentation sections label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: new content PRs for new product features or new documentation sections source: Dev Docs PRs/issues targeting the Developer Docs v5 Documentation PR that targets Strapi v5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants