i18n(fr): update plugins and utils#156
Conversation
✅ Deploy Preview for studiocms-dev-docs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughTwo documentation files were updated. The French plugins documentation now describes a new Changes
Sequence Diagram(s)sequenceDiagram
participant PluginDev as Plugin Developer
participant StudioCMS as StudioCMS Plugin System
PluginDev->>StudioCMS: Call setAuthService({ oAuthProvider })
StudioCMS-->>PluginDev: Registers OAuth provider details for authentication
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
src/content/docs/fr/utils/rendering.mdx (1)
18-20: Reformuler l’aside pour plus de concision
La phrase est un peu longue et contient des répétitions (« module d’extension … fournissant un moteur de rendu » apparaît deux fois). Une formulation plus concise améliorera la lisibilité sans altérer le contenu technique.-Veuillez noter que l’utilisation de notre système de rendu nécessite que vous disposiez d’un module d’extension pour StudioCMS fournissant un moteur de rendu, tel que `@studiocms/md`, `@studiocms/html` ou un module d’extension personnalisé qui fournit un moteur de rendu pour votre type de contenu. Le moteur de rendu gérera le rendu du contenu en fonction du type de page défini dans votre configuration de StudioCMS. +Veuillez noter que le système de rendu de StudioCMS requiert un module d’extension fournissant un moteur de rendu (par ex. `@studiocms/md`, `@studiocms/html` ou un module personnalisé). +Ce moteur se charge d’afficher le contenu selon le type de page déclaré dans votre configuration StudioCMS.src/content/docs/fr/plugins/index.mdx (1)
77-85: Mettre l’exemple complet à jour pour illustrersetAuthService
Le bloc d’exemple situé plus bas (lignes 101-130) ne montre pas encore l’utilisation desetAuthService. Ajouter un court extrait renforcerait la compréhension de cette nouvelle API.@@ hooks: { 'studiocms:astro:config': ({ addIntegrations }) => { addIntegrations(monIntegration(options)) // Facultatif, mais recommandé }, + 'studiocms:config:setup': ({ setAuthService }) => { + setAuthService({ + oAuthProvider: { + name: 'github', + formattedName: 'GitHub', + svg: '<svg>…</svg>', + endpointPath: '/api/auth/github', + requiredEnvVariables: ['GITHUB_CLIENT_ID', 'GITHUB_CLIENT_SECRET'] + } + }) + } } } });
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/content/docs/fr/plugins/index.mdx(1 hunks)src/content/docs/fr/utils/rendering.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#149
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-21.mdx:13-15
Timestamp: 2025-07-24T11:57:15.225Z
Learning: In the withstudiocms/docs repository, when reviewing French translation files, maintain consistency with the English version even if it means keeping unused imports. Structural parity between language versions is prioritized over removing unused code.
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#149
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-20.mdx:18-18
Timestamp: 2025-07-24T12:00:35.014Z
Learning: In the withstudiocms/docs repository, while translations should maintain structural parity with English versions, improving readability during translation is acceptable when the original text has clear redundancy or readability issues that would also impact the translation quality. The maintainer ArmandPhilippot confirmed this approach is reasonable when the technical meaning is preserved.
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#130
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-17.mdx:1-11
Timestamp: 2025-04-26T12:29:17.995Z
Learning: When reviewing translations in the withstudiocms/docs repository, compare with the corresponding English version as the source of truth, not with other files in the same target language. French translations should maintain structural parity with their English counterparts.
📚 Learning: in the withstudiocms/docs repository, documentation urls in the package-catalog may maintain legacy ...
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
Applied to files:
src/content/docs/fr/utils/rendering.mdx
🪛 LanguageTool
src/content/docs/fr/utils/rendering.mdx
[uncategorized] ~16-~16: Le trait d’union doit être supprimé.
Context: ...el. Exemple d’une route fourre-tout (« catch-all » en anglais) où la page actuelle est r...
(MOT_TRAIT_MOT)
[typographical] ~16-~16: Caractère d’apostrophe incorrect.
Context: ...ge comme nous le faisons avec le plugin @studiocms/blog. Un plugin de création de pages, par ex...
(APOS_INCORRECT)
[style] ~16-~16: Une phrase longue peut apporter une perte de sens pour le lecteur. Celle-ci peut donc être divisée afin d’apporter de la clarté et du rythme.
Context: ...t être fourni sans mise en page standard, parce qu’il vise plutôt à ce que vous conceviez l...
(POINT_MAIS)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Run Starlight Link Check
- GitHub Check: Redirect rules - studiocms-dev-docs
- GitHub Check: Header rules - studiocms-dev-docs
- GitHub Check: Pages changed - studiocms-dev-docs
🔇 Additional comments (2)
src/content/docs/fr/utils/rendering.mdx (1)
12-13: Import statement looks correct
L’import du composantAsidedepuis@astrojs/starlight/componentsest conforme à la convention employée dans le reste de la documentation.src/content/docs/fr/plugins/index.mdx (1)
77-85: Bien vu ! L’APIsetAuthServiceest correctement intégrée
La nouvelle définition reflète fidèlement la version anglaise : propriétés, typage optionnel et cohérence de l’indentation sont respectés.
3 participants
Description
Adds changes from #150 and #151 to the French translations of
plugins/index.mdxandutils/rendering.mdx.Summary by CodeRabbit