feat(ja): update more outdated Japanese documentation #3974
Merged
Conversation
Update Japanese translations for 11 documentation files to match the latest English versions: - Add extension settings section to create-an-extension.mdx - Add Nova extension to third-party-extensions.mdx - Update VCS integration with .ignore file support - Add Scanner section to architecture.mdx - Add Core Contributors and Maintainers to people-and-credits.mdx - Add version pinning importance to versioning.mdx - Add biome ci explanation and GitLab CI to continuous-integration.mdx - Remove experimental tag and add new sections to gritql.mdx - Add inlineConfig setting to vscode.mdx - Restructure and update zed.mdx with inline_config section 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
✅ Deploy Preview for biomejs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
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
|
Update Japanese translation for getting-started.mdx to match the latest English version: - Simplify installation instructions to match current structure - Update package manager commands with shorter syntax - Restructure usage section with tabs for different package managers - Add Editor integrations section with first-party extensions - Add Continuous Integration section with GitHub Actions and GitLab CI links - Update Next Steps section links 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
WalkthroughThis PR updates Japanese documentation across the site. Changes include new editor-extension settings (require_configuration / configuration_path / inline_config) and expanded Zed and VS Code guidance; a tabbed commands UI and install matrix in the getting-started guide; a new "スキャナー" (Scanner) section in architecture; TypeScript support bumped to 5.9; CI recipe additions for Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
src/content/docs/ja/guides/integrate-in-vcs.mdx (1)
23-23: Clarify which ignore files are included (e.g.,.gitignore, project‑root.ignore).
This line reads a bit broad; a tiny hint or example would help readers avoid ambiguity.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/ja/guides/integrate-in-vcs.mdx` at line 23, The sentence for vcs.useIgnoreFile is too broad — update the text around the vcs.useIgnoreFile setting to explicitly list which ignore files are considered (for example: .gitignore, project-root .ignore, and other common VCS ignore files such as .hgignore) and clarify whether Biome reads only the project root files or also nested/parent directories; mention the typical behavior (e.g., "Biome ignores files listed in .gitignore and the project's root .ignore") so readers know exact scope.src/content/docs/ja/reference/vscode.mdx (1)
142-175: Missing setting metadata for consistency.Other settings in this file include デフォルト: and スコープ: metadata (e.g., lines 115-116, 126-127, 132-133). Consider adding these for
biome.inlineConfigto maintain consistency:Suggested addition after line 142
### `biome.inlineConfig` + +**デフォルト:** `null` | **スコープ:** `global`, `workspace`, `workspace folder` Biome設定のインラインバージョン。この設定のオプションは、ディスクから読み取られた `biome.json` ファイル（またはデフォルト値）のオプションを上書きします。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/ja/reference/vscode.mdx` around lines 142 - 175, The `biome.inlineConfig` setting documentation is missing the consistent metadata blocks other settings have; update the `biome.inlineConfig` section to include the same metadata lines (e.g., "デフォルト:" and "スコープ:") directly after the `### \`biome.inlineConfig\`` heading so it matches the other entries such as the ones around lines 115–133 and preserves documentation consistency.src/content/docs/ja/reference/zed.mdx (2)
136-148: Avoid duplicating the require_config_file example. This repeats the earlier section; a short cross-reference would keep things tighter.Proposed tidy-up
### biome.jsonが存在する場合にのみBiomeを有効にする - -```json5 title=".zed/settings.json" -{ - "lsp": { - "biome": { - "settings": { - "require_config_file": true - } - } - } -} -``` +`require_config_file` の説明と設定例は、上記の「require_config_file」セクションを参照してください。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/ja/reference/zed.mdx` around lines 136 - 148, Remove the duplicated JSON snippet showing require_config_file in the Biome section and replace it with a short cross-reference pointing to the earlier "require_config_file" section; specifically delete the JSON block that starts with `.zed/settings.json` and the nested "lsp.biome.settings.require_config_file" example and instead insert a one-line note like "require_config_file の説明と設定例は、上記の「require_config_file」セクションを参照してください。" so readers are directed to the original example.
182-185: Consider tightening the wording here. Dropping “ことができます” reads cleaner.Suggested wording tweak
-これらの設定は、プロジェクトフォルダのルートにあるZedプロジェクト設定（`.zed/settings.json`）に含めるか、すべてのプロジェクトにデフォルトで適用されるZedユーザー設定（`~/.config/zed/settings.json`）に含めることができます。 +これらの設定は、プロジェクトフォルダのルートにあるZedプロジェクト設定（`.zed/settings.json`）に含めるか、すべてのプロジェクトにデフォルトで適用されるZedユーザー設定（`~/.config/zed/settings.json`）に含められます。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/ja/reference/zed.mdx` around lines 182 - 185, Tighten the Japanese wording by removing the trailing "ことができます" to make the sentence more direct; update the sentence that references the Zed project settings path `.zed/settings.json` and the user settings path `~/.config/zed/settings.json` so it reads that these settings are included in those locations (drop "ことができます") and ensure punctuation and spacing remain correct.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/ja/guides/editors/first-party-extensions.mdx`:
- Line 42: The keyboard shortcut string "<kbd>⌘</kbd> /
<kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd> + <kbd>,</kbd>" is malformed; update
the sentence in the document to show separate platform-specific shortcuts
instead of merging them — replace the combined "<kbd>⌘</kbd> /
<kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd> + <kbd>,</kbd>" fragment with two
alternatives, e.g. "macOS: <kbd>⌘</kbd>+<kbd>,</kbd>" and "Windows/Linux:
<kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd>", keeping the surrounding text
("を押してIDE設定を開き、プラグインを選択します。") unchanged.
---
Nitpick comments:
In `@src/content/docs/ja/guides/integrate-in-vcs.mdx`:
- Line 23: The sentence for vcs.useIgnoreFile is too broad — update the text
around the vcs.useIgnoreFile setting to explicitly list which ignore files are
considered (for example: .gitignore, project-root .ignore, and other common VCS
ignore files such as .hgignore) and clarify whether Biome reads only the project
root files or also nested/parent directories; mention the typical behavior
(e.g., "Biome ignores files listed in .gitignore and the project's root
.ignore") so readers know exact scope.
In `@src/content/docs/ja/reference/vscode.mdx`:
- Around line 142-175: The `biome.inlineConfig` setting documentation is missing
the consistent metadata blocks other settings have; update the
`biome.inlineConfig` section to include the same metadata lines (e.g., "デフォルト:"
and "スコープ:") directly after the `### \`biome.inlineConfig\`` heading so it
matches the other entries such as the ones around lines 115–133 and preserves
documentation consistency.
In `@src/content/docs/ja/reference/zed.mdx`:
- Around line 136-148: Remove the duplicated JSON snippet showing
require_config_file in the Biome section and replace it with a short
cross-reference pointing to the earlier "require_config_file" section;
specifically delete the JSON block that starts with `.zed/settings.json` and the
nested "lsp.biome.settings.require_config_file" example and instead insert a
one-line note like "require_config_file
の説明と設定例は、上記の「require_config_file」セクションを参照してください。" so readers are directed to the
original example.
- Around line 182-185: Tighten the Japanese wording by removing the trailing
"ことができます" to make the sentence more direct; update the sentence that references
the Zed project settings path `.zed/settings.json` and the user settings path
`~/.config/zed/settings.json` so it reads that these settings are included in
those locations (drop "ことができます") and ensure punctuation and spacing remain
correct.
siketyan
force-pushed
the
feat/update-ja-docs
branch
from
d68c0ca to
6ca640e
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/ja/guides/getting-started.mdx`:
- Line 182: The inline link "[CLIコマンドとオプション](/reference/cli)" is missing the
Japanese locale prefix and should be updated to match surrounding links; change
the href to "/ja/reference/cli" so the link becomes
"[CLIコマンドとオプション](/ja/reference/cli)" to ensure consistency with the other
Japanese documentation links.
- Line 43: The link definition "[コマンドラインインターフェース]: /reference/cli" is missing
the Japanese path prefix; update that link target to include the /ja/ prefix
(i.e., change the target to /ja/reference/cli) so the link points to the
Japanese CLI reference in this file (look for the exact string
"[コマンドラインインターフェース]: /reference/cli" in
src/content/docs/ja/guides/getting-started.mdx).
- Line 12: Update the markdown link target for the link text "[スタンドアロン実行形式]" so
it uses the Japanese-docs prefix; replace "/guides/manual-installation" with
"/ja/guides/manual-installation" in the line containing that link to match other
links in this file (e.g., the one on line 27).
- Around line 110-130: Reorder the command blocks inside the TabItem with
label="deno" so the "すべてのファイルをフォーマット" (format all files) entry appears before
the "特定のファイルをフォーマット" (format specific files) entry to match the command order
used in the other tabs; edit the JSX inside the Code component (code={...}) in
the TabItem label="deno" to swap those two blocks while keeping the rest of the
commands and formatting unchanged.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@src/content/docs/ja/guides/getting-started.mdx`:
- Around line 39-43: The CLI reference link in the Japanese guide uses the
English path "/reference/cli"; update the markdown link target for
"[コマンドラインインターフェース]" to the Japanese path "/ja/reference/cli" so it matches other
Japanese links in the file (edit the link target string "/reference/cli" to
"/ja/reference/cli" in src/content/docs/ja/guides/getting-started.mdx).
- Around line 178-183: Update the CLI next-step link to include the Japanese
prefix: replace the link target for "[CLIコマンドとオプション](/reference/cli)" with the
localized path "/ja/reference/cli" in the getting-started page so the link
points to the Japanese CLI reference; ensure you only change the href portion
and keep the link text unchanged.
- Around line 110-117: Reorder the two code blocks inside the TabItem with
label="deno" so the "format all" command appears before the "format specific
files" command to match the other tabs; locate the <TabItem label="deno"> block
and swap the two Code component contents (the Code showing "deno run -A
npm:`@biomejs/biome` format --write" and the Code showing "deno run -A
npm:`@biomejs/biome` format --write <files>") so the non-argument (format all)
invocation is listed first.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Note
AI Disclosure: I used Claude Agent to create the first draft of this PR (see d55ff12). All the changes have been reviewed and revised by me.
Update more outdated Japanese docs corresponding to the following pages: