docs: update README to clarify translation validation features and improve formatting#36
Conversation
WalkthroughThe README file was updated to clarify and expand the description of the Changes
Possibly related PRs
Poem
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. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
README.md (3)
13-14: Singularize “translations mismatches”Minor grammar nit ‒ “translations mismatches” should be “translation mismatches”.
-Provides a command `validate-translations` to check for translations mismatches, duplicates, schema validation and more. +Provides a command `validate-translations` to check for translation mismatches, duplicates, schema validation, and more.
70-73: Tautology & wording polish in “Supports yaml language files”Both “YAML” and “JSON” already imply “language”, so the extra word is redundant. While you’re here, you could also align the descriptions for consistency (they currently vary in brevity).
-| [YAML](https://en.wikipedia.org/wiki/YAML) | Supports yaml language files. | [Symfony](https://symfony.com/) | `messages.en.yaml`, `messages.de.yaml` | -| [JSON](https://en.wikipedia.org/wiki/JSON) | Supports JSON language files with nested key support. | [Laravel](https://laravel.com/) / [Symfony](https://symfony.com/) | `messages.en.json`, `messages.de.json` | +| [YAML](https://en.wikipedia.org/wiki/YAML) | Supports YAML translation files. | [Symfony](https://symfony.com/) | `messages.en.yaml`, `messages.de.yaml` | +| [JSON](https://en.wikipedia.org/wiki/JSON) | Supports JSON translation files (nested keys supported). | [Laravel](https://laravel.com/) / [Symfony](https://symfony.com/) | `messages.en.json`, `messages.de.json` |
81-90: Inline<span style="color:#…">won’t render on GitHubGitHub strips most inline styles for security reasons; the coloured severity labels will fall back to plain text.
Consider alternatives:
- Use emoji: 🚨 /
⚠️ - Use Shields.io badges.
- Keep plain text but rely on column order to convey severity.
If colour is important, option 2 provides the clearest visual cue while staying GitHub-safe.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(3 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md
[style] ~70-~70: This phrase is redundant (‘L’ stands for ‘language’). Use simply “yaml”.
Context: ...n.wikipedia.org/wiki/YAML) | Supports yaml language files. | [Symfony](...
(ACRONYM_TAUTOLOGY)
🔇 Additional comments (1)
README.md (1)
19-21: Nice touch adding deep-linksLinking to the dedicated sections improves discoverability and saves readers extra scrolling.
Summary by CodeRabbit
validate-translationscommand.