feat: fix LSP configuration for Claude Code integration - #310
Conversation
- Fix plugin.json to use correct lspServers key (not languageServers) - Use extensionToLanguage mapping (not filetypes) - Add setup-lsp.sh script for automatic Language Server installation - Update devcontainer.json to run setup-lsp.sh in postCreateCommand - Update npm/global.json with latest Language Server versions - Update devcontainer-checklist.md with correct LSP configuration format 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
📝 WalkthroughWalkthroughRenames top-level LSP config key Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant DevContainer
participant SetupScript as script/setup-lsp.sh
participant NPM
participant LSPs as LanguageServers
participant Verifier
DevContainer->>SetupScript: run postCreateCommand -> invoke setup-lsp.sh
SetupScript->>NPM: npm install -g [tsc, typescript-language-server, bash-language-server, vscode-json-language-server, yaml-language-server]
NPM-->>LSPs: install binaries globally
SetupScript->>Verifier: check binaries (tsc, typescript-language-server, bash-language-server, yaml-language-server, vscode-json-language-server)
Verifier-->>SetupScript: report OK / MISSING per binary
SetupScript->>DevContainer: print summary (all OK or missing count)
DevContainer->>DevContainer: continue with remaining postCreateCommand (e.g., setup-claude)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Poem
Pre-merge checks❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
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. Comment |
プルリクエストレビュー概要Claude CodeのLSP設定を修正し、Language Serverの自動セットアップスクリプトを追加するPRです。変更内容は的確で、品質基準を満たしています。 ✅ Good Points1. 正しいAPI形式への修正
2. 拡張子の網羅性TypeScript設定で 3. 自動化スクリプト
4. 堅牢なエラーハンドリング
5. ドキュメント更新
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
.claude-plugin/plugin.json.claude/commands/devcontainer-checklist.md.devcontainer/devcontainer.jsonnpm/global.jsonscript/setup-lsp.sh
🧰 Additional context used
📓 Path-based instructions (1)
{.codex/**,.devcontainer/codex*,package*.json,npm/global.json}
📄 CodeRabbit inference engine (CLAUDE.md)
Use Conventional Commits format with release-triggering types (feat/fix/perf/revert/docs) for commits touching .codex/**, .devcontainer/codex*, package*.json, or npm/global.json
Files:
npm/global.json
🧠 Learnings (5)
📚 Learning: 2026-01-04T04:05:56.900Z
Learnt from: CR
Repo: keito4/config PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-04T04:05:56.900Z
Learning: Use automated Claude commands from `.claude/commands/` directory for maintenance, Git workflows, code analysis, quality checks, dependency management, security reviews, and tool configuration
Applied to files:
.devcontainer/devcontainer.json.claude/commands/devcontainer-checklist.md
📚 Learning: 2026-01-04T04:05:56.900Z
Learnt from: CR
Repo: keito4/config PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-04T04:05:56.900Z
Learning: Follow development quality standards defined in `CLAUDE.md` for AI-assisted development workflows
Applied to files:
.claude/commands/devcontainer-checklist.md
📚 Learning: 2026-01-04T04:05:56.900Z
Learnt from: CR
Repo: keito4/config PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-04T04:05:56.900Z
Learning: Refer to `CLAUDE.md` for quality standards, AI prompt design guidelines, and CI integration
Applied to files:
.claude/commands/devcontainer-checklist.md
📚 Learning: 2026-01-04T04:05:56.900Z
Learnt from: CR
Repo: keito4/config PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-04T04:05:56.900Z
Learning: Use specialized Claude Code agents from `.claude/agents/` directory for architecture validation, performance analysis, concurrency safety, and testability analysis
Applied to files:
.claude/commands/devcontainer-checklist.md
📚 Learning: 2025-12-01T03:45:17.253Z
Learnt from: CR
Repo: keito4/config PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-01T03:45:17.253Z
Learning: Applies to .github/workflows/claude.yml : Trigger automatic AI assistance on claude mentions in issues, PRs, and comments using .github/workflows/claude.yml
Applied to files:
.claude/commands/devcontainer-checklist.md
⏰ 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). (3)
- GitHub Check: claude-review
- GitHub Check: Trivy Container Scan
- GitHub Check: Generate SBOM
🔇 Additional comments (9)
script/setup-lsp.sh (2)
32-50: LGTM!The
verify_commandfunction is well-structured with proper error handling. The|| ((errors++))pattern correctly counts failures without triggeringset -e.
15-26: LGTM!The language server list is comprehensive and matches the verification checks. Global installation is appropriate for LSP binaries.
.claude-plugin/plugin.json (2)
5-17: LGTM!The
lspServerskey and TypeScriptextensionToLanguagemappings are comprehensive, covering all common JavaScript/TypeScript file extensions including ESM (.mjs) and CommonJS (.cjs).
18-33: LGTM!Bash and JSON server configurations look correct with appropriate extension-to-language mappings.
.devcontainer/devcontainer.json (1)
53-53: LGTM!The
setup-lsp.shscript is correctly integrated into the postCreateCommand chain, positioned after dependency installation and before the final Claude setup.Note: Per the review of
setup-lsp.sh, if that script's exit code is changed to propagate errors, ensure the DevContainer build won't fail unexpectedly on LSP installation issues..claude/commands/devcontainer-checklist.md (3)
93-104: LGTM!Documentation correctly reflects the new
lspServerskey andextensionToLanguageproperty. Thejqverification command is helpful for troubleshooting.
301-314: LGTM!The troubleshooting section is well-updated with the new setup script reference and clear guidance about the deprecated configuration format.
353-353: LGTM!Version reference updated to align with the DevContainer base image version in
devcontainer.json.npm/global.json (1)
24-46: Version updates are valid and align with the LSP setup workflow.All updated packages (
bash-language-server@5.6.0,typescript@5.9.3,typescript-language-server@5.1.3,yaml-language-server@1.19.2) exist on npm and are consistent with the new LSP installation requirements.Likely an incorrect or invalid review comment.
| "extensionToLanguage": { | ||
| ".yaml": "yaml", | ||
| ".yml": "yml" | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat .claude-plugin/plugin.jsonRepository: keito4/config
Length of output: 1061
🌐 Web query:
YAML language identifier LSP language server protocol
💡 Result:
-
Standard LSP language identifier (languageId) for YAML: "yaml". [1]
-
Common YAML LSP server: Red Hat's yaml-language-server (invoked as the binary
yaml-language-server, client name oftenyamlls), typically started withyaml-language-server --stdio. [2]
Sources: [1] Red Hat yaml-language-server README; [2] lsp-mode / nvim-lsp docs.
Change .yml extension mapping from "yml" to "yaml".
The .yml extension currently maps to the language identifier "yml", while .yaml maps to "yaml". According to LSP standards, the correct language identifier for YAML files is "yaml". Both extensions should map to the same identifier for consistent language server initialization.
Current code (lines 37-40)
"extensionToLanguage": {
".yaml": "yaml",
".yml": "yml"
}
Change ".yml": "yml" to ".yml": "yaml".
🤖 Prompt for AI Agents
In .claude-plugin/plugin.json around lines 37 to 40, the extensionToLanguage
mapping maps ".yml" to the incorrect identifier "yml"; change the value for
".yml" to "yaml" so both ".yaml" and ".yml" map to the standard "yaml" language
identifier per LSP conventions.
| # Language Server Protocol Setup Script | ||
| # Installs language servers required for Claude Code LSP integration | ||
|
|
||
| set -e |
There was a problem hiding this comment.
Consider propagating failure status via exit code.
The script uses set -e but unconditionally exits with 0 even when language servers are missing. This masks failures from the calling process (devcontainer postCreateCommand), making troubleshooting harder if LSP installation silently fails.
🔎 Proposed fix to propagate error status
if [ $errors -eq 0 ]; then
echo "=== All Language Servers installed successfully ==="
else
echo "=== Warning: $errors language server(s) missing ==="
fi
-exit 0
+exit $errorsIf a non-zero exit would break the DevContainer build, consider making it configurable or at least documenting the intentional silent failure behavior.
Also applies to: 53-59
🤖 Prompt for AI Agents
In script/setup-lsp.sh around lines 5 and 53-59, the script currently uses set
-e but ends by unconditionally exiting with 0 which hides failures; modify the
flow so the script returns a non-zero exit code when any LSP install or check
fails (e.g., track a failure flag or capture command exit statuses and exit with
that code), or make this behavior configurable via an environment variable
(e.g., SKIP_LSP_ERRORS=true to preserve an exit 0) and document the default to
fail the DevContainer postCreateCommand; ensure any early returns respect set -e
and propagate the actual error code instead of always exiting 0.
Add config-lsp to enabledPlugins to activate the local LSP configuration. Without this setting, the LSP servers defined in .claude-plugin/plugin.json are not loaded by Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.claude/settings.json
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-01-04T04:05:56.900Z
Learnt from: CR
Repo: keito4/config PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-04T04:05:56.900Z
Learning: Follow development quality standards defined in `CLAUDE.md` for AI-assisted development workflows
Applied to files:
.claude/settings.json
⏰ 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). (3)
- GitHub Check: claude-review
- GitHub Check: Generate SBOM
- GitHub Check: Trivy Container Scan
| "deny": [] | ||
| }, | ||
| "enabledPlugins": { | ||
| "config-lsp": true, |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check if the files mentioned exist and explore the structure
git ls-files | grep -E "(claude|settings|plugin)" | head -20Repository: keito4/config
Length of output: 850
🏁 Script executed:
# Look at the .claude/settings.json file to verify the change context
if [ -f ".claude/settings.json" ]; then
echo "=== .claude/settings.json ==="
cat -n ".claude/settings.json" | head -120
else
echo "File not found"
fiRepository: keito4/config
Length of output: 4252
🏁 Script executed:
# Check if .claude-plugin/plugin.json exists
if [ -f ".claude-plugin/plugin.json" ]; then
echo "=== .claude-plugin/plugin.json ==="
cat ".claude-plugin/plugin.json"
else
echo "File not found"
fiRepository: keito4/config
Length of output: 1096
🏁 Script executed:
# Look for CLAUDE.md to understand development quality standards
if [ -f "CLAUDE.md" ]; then
echo "=== CLAUDE.md ==="
cat "CLAUDE.md"
else
echo "CLAUDE.md not found in root"
fiRepository: keito4/config
Length of output: 4030
🏁 Script executed:
# Check if there are any references to "config-lsp" plugin in the codebase
rg "config-lsp" --type jsonRepository: keito4/config
Length of output: 39
LGTM! Verify LSP functionality before merging.
The addition of "config-lsp": true correctly enables the local LSP plugin configuration defined in .claude-plugin/plugin.json, which aligns with the PR's objective to fix LSP configuration for Claude Code integration.
Per the PR test plan, DevContainer LSP verification is incomplete. Please ensure the TypeScript, Bash, JSON, and YAML language servers integrate correctly with Claude Code and provide expected functionality in the DevContainer environment before merging.
🤖 Prompt for AI Agents
In .claude/settings.json around line 107, you enabled "config-lsp": true but
haven’t verified LSP functionality in the DevContainer; follow the PR test plan
to validate and fix integration: start the DevContainer, open representative
TypeScript, Bash, JSON, and YAML files, confirm language servers activate,
diagnostics/hover/completion/formatting work with Claude Code, inspect extension
and plugin logs for errors, adjust plugin.json or settings.json (e.g., server
paths, activation events, workspaceFolder mappings, environment variables) or
install missing language-server binaries as needed, and document the
verification steps and any fixes before merging.
PR Review: LSP Configuration Fix✅ 良い点 (Strengths)
|
| 項目 | 状態 | 備考 |
|---|---|---|
| Format Check | ✅ | パス |
| Lint | ✅ | パス |
| Test (101/101) | ✅ | パス |
| Test Coverage (TDD) | LSP設定の単体テスト未実装 | |
| ShellCheck | ✅ | パス |
| Security Scan | ✅ | パス |
| Documentation | ✅ | 適切に更新済み |
🎯 総合評価
推奨アクション: Approve with minor changes
このPRは明確な問題を解決する良い修正ですが、以下の対応を推奨します：
- Critical: TypeScriptバージョンを実在するものに修正
- Recommended: テストカバレッジ追加（TDD原則準拠）
- Optional: エラーハンドリング強化
修正後は .claude/CLAUDE.md の Definition of Done 基準を満たします。
レビュー基準: CLAUDE.md Section 2 (Development Philosophy), Section 7 (Quality Gates)
Add ENABLE_LSP_TOOL=1 to remoteEnv in devcontainer.json. This environment variable is required for Claude Code to enable the LSP tool functionality. Reference: https://blog.lai.so/claude-code-lsp/ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
PR Review SummaryこのPRは Claude Code の LSP 設定を修正する重要な変更です。全体的に実装は適切ですが、いくつかの改善提案があります。 ✅ Good Points
🔍 Potential Issues & Improvements1. セキュリティ: エラーハンドリングの強化
2. パフォーマンス: npm install の冗長性既にインストール済みのパッケージを再インストールする可能性があります。バージョンチェックを追加して、必要な場合のみインストールすることを推奨します。 3. テストカバレッジの欠如新規追加された 4. ドキュメント: npm/global.json のバージョン更新理由以下のパッケージバージョンが更新されていますが、PR の説明に変更理由が記載されていません：
破壊的変更やセキュリティパッチの有無を PR 説明に追加してください。 📋 Test Plan Status
質問: DevContainer での実環境テストは完了していますか？ 🔒 Security Considerations
🎯 Recommendations Summary
総評LSP 設定の修正は正しく、Claude Code との統合を大幅に改善する変更です。上記の改善提案に対応すれば、マージ可能です。 推奨アクション: DevContainer 再ビルドテストの完了後、エラーハンドリングを強化してマージ 🤖 Generated with Claude Code |
Move LSP server definitions to .lsp.json file at project root and reference it from plugin.json. This follows the recommended structure from the Claude Code documentation. Reference: https://azukiazusa.dev/blog/claude-code-lsp-support/ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Pull Request Review - PR #310総合評価 ✅このPRは、Claude CodeのLSP設定を修正する重要な改善です。設定形式の誤りを正し、自動セットアップスクリプトを追加しています。全体的に品質が高く、リポジトリの品質基準を満たしています。 📋 レビューサマリ
✅ 良い点1. 設定形式の修正（.claude-plugin/plugin.json:5）
2. 包括的なLSP設定（.lsp.json:1-38）
3. 自動セットアップスクリプト（script/setup-lsp.sh）
4. ドキュメント更新
|
| 基準 | 状態 | 備考 |
|---|---|---|
| TDD | スクリプトのテストがない | |
| Static Quality Gates | ✅ | format:check, lint, shellcheck パス |
| Git Workflow | ✅ | Conventional Commits準拠 |
| Code Coverage | N/A | 設定ファイルのため対象外 |
| Documentation | ✅ | チェックリストとトラブルシューティング更新済み |
🎯 推奨アクション
必須（Must）
- TypeScriptバージョン（5.9.3）が正しいか確認
推奨（Should）
- script/setup-lsp.sh のエラーハンドリング改善
- .lsp.json に rootPatterns を追加
- postCreateCommand を配列形式に変更
オプション（Could）
- setup-lsp.sh の自動テスト追加
- LSP設定のJSON schemaバリデーション
🏁 結論
このPRは、LSP設定の重要な修正を含む高品質な変更です。小さな改善点はありますが、現状でもマージ可能な品質です。上記の改善提案を検討いただければ、さらに堅牢な実装になります。
マージ推奨度: ✅ 承認（Minor改善後が理想）
レビュー実施日: 2026-01-04
レビュアー: Claude Code (Automated Review)
There was a problem hiding this comment.
Actionable comments posted: 3
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.claude-plugin/plugin.json.lsp.json
🚧 Files skipped from review as they are similar to previous changes (1)
- .claude-plugin/plugin.json
⏰ 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). (3)
- GitHub Check: claude-review
- GitHub Check: Trivy Container Scan
- GitHub Check: Generate SBOM
🔇 Additional comments (1)
.lsp.json (1)
22-29: The JSON configuration correctly includes both.jsonand.jsoncwith appropriate language identifiers. Thevscode-json-language-servercommand is part of thevscode-langservers-extractedpackage and is verified by your setup script.
| "typescript": { | ||
| "command": "typescript-language-server", | ||
| "args": ["--stdio"], | ||
| "extensionToLanguage": { | ||
| ".js": "javascript", | ||
| ".jsx": "javascriptreact", | ||
| ".ts": "typescript", | ||
| ".tsx": "typescriptreact", | ||
| ".mjs": "javascript", | ||
| ".cjs": "javascript" | ||
| } | ||
| }, |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for .cts and .mts files in the repository
fd -e cts -e mts
# Check for package.json and typescript configuration
find . -name "package.json" -o -name "tsconfig.json" | head -20
# Display the .lsp.json file to see full context
cat -n .lsp.json 2>/dev/null || echo "File not found at root"Repository: keito4/config
Length of output: 1127
Fix incorrect YAML extension language mapping.
The TypeScript server command typescript-language-server is correct. However, line 35 has an issue: the .yml extension should map to "yaml" (not "yml"), as "yaml" is the VSCode language identifier for both .yaml and .yml files.
🤖 Prompt for AI Agents
In .lsp.json around lines 2 to 13, the language mapping for the YAML file
extension is incorrect; update the mapping so that ".yml" maps to "yaml" (the
VSCode language identifier) instead of "yml" — ensure any YAML extension entries
(e.g., ".yml", and optionally ".yaml") use the value "yaml".
| "bash": { | ||
| "command": "bash-language-server", | ||
| "args": ["start"], | ||
| "extensionToLanguage": { | ||
| ".sh": "sh", | ||
| ".bash": "bash" | ||
| } | ||
| }, |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
bash-language-server npm configuration command arguments --stdio
💡 Result:
Use the "start" subcommand — you do not pass a separate --stdio flag. Example editor/client configs:
-
coc.nvim / VSCode settings:
"language.bash.languageServer.command": "bash-language-server",
"language.bash.languageServer.arguments": ["start"]. [1][2] -
nvim-lspconfig (Lua):
cmd = { "bash-language-server", "start" }. [3]
The server speaks the Language Server Protocol over stdio when started with "start", so no explicit --stdio argument is required. [1][3]
Sources:
[1] npm bash-language-server README.
[2] npm package documentation examples.
[3] GitHub bash-language-server README.
🌐 Web query:
language identifiers shell bash sh vscode lsp languageId
💡 Result:
Short answer:
- VS Code's built-in Shell Script language identifier is "shellscript". [1]
- Some extensions may define their own ids (e.g. an extension could use "bash" — check the extension's package.json). [1]
- For the Language Server Protocol, the editor sends the languageId (e.g. "shellscript") in the initialize/didOpen notifications; extensions declare their language id in package.json under "languages". [1][2]
How to confirm / use it:
- See the known identifiers list (shows Shell Script → "shellscript"). [1]
- To associate files: add to settings.json:
"files.associations": { "*.sh": "shellscript", "myfile": "shellscript" }. [1] - To find an installed language's id in VS Code: open Change Language Mode (Ctrl/Cmd+K M) or inspect an extension's package.json "languages" entry. [2]
Sources:
[1] Visual Studio Code — Language Identifiers (official docs).
[2] Visual Studio Code — Programming Languages / Language identifier (official docs).
🏁 Script executed:
cat -n .lsp.json | head -50Repository: keito4/config
Length of output: 1112
Update Bash language identifiers to match VS Code standard.
The bash configuration correctly uses "start" as the argument (this is the correct subcommand for bash-language-server), but the language identifiers are incorrect. VS Code's standard Shell Script identifier is "shellscript", not "sh" and "bash".
Update the extensionToLanguage mapping:
"extensionToLanguage": {
".sh": "shellscript",
".bash": "shellscript"
}This matches the pattern used by other servers in this file and ensures the language server receives file notifications for shell scripts.
🤖 Prompt for AI Agents
In .lsp.json around lines 14 to 21, the bash language mapping uses nonstandard
identifiers ("sh" and "bash"); update the extensionToLanguage mapping so both
".sh" and ".bash" map to VS Code's standard "shellscript" identifier to ensure
the bash-language-server receives proper file notifications.
| "yaml": { | ||
| "command": "yaml-language-server", | ||
| "args": ["--stdio"], | ||
| "extensionToLanguage": { | ||
| ".yaml": "yaml", | ||
| ".yml": "yml" | ||
| } | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
VSCode language identifier yaml yml correct standard
💡 Result:
Use the language identifier "yaml" (lowercase). VS Code's built-in language id is "yaml"; both file extensions ".yaml" and ".yml" are supported by YAML language extensions. Example settings entry: "files.associations": { ".yml": "yaml", ".yaml": "yaml" }. [1][2]
Sources:
[1] VS Code Language Identifiers (built‑in list) — YAML = "yaml".
[2] redhat-developer vscode-yaml (YAML support/extension; recognizes .yaml/.yml).
🌐 Web query:
yaml-language-server correct command name npm package
💡 Result:
The npm package is named "yaml-language-server" and the CLI command it installs is yaml-language-server (commonly run as yaml-language-server --stdio). [1][2]
Sources:
- npm package page for yaml-language-server. [1]
- yaml-language-server README / docs showing
node .../server.js [--stdio]/ usage (--stdio). [2]
Fix YAML language identifier mapping.
Line 35 maps .yml to "yml", but VSCode language identifiers use "yaml" (lowercase) for both .yaml and .yml files. This will cause .yml files to not be properly recognized by the language server. The command name yaml-language-server and --stdio argument are correct.
Fix
"yaml": {
"command": "yaml-language-server",
"args": ["--stdio"],
"extensionToLanguage": {
".yaml": "yaml",
- ".yml": "yml"
+ ".yml": "yaml"
}
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "yaml": { | |
| "command": "yaml-language-server", | |
| "args": ["--stdio"], | |
| "extensionToLanguage": { | |
| ".yaml": "yaml", | |
| ".yml": "yml" | |
| } | |
| } | |
| "yaml": { | |
| "command": "yaml-language-server", | |
| "args": ["--stdio"], | |
| "extensionToLanguage": { | |
| ".yaml": "yaml", | |
| ".yml": "yaml" | |
| } | |
| } |
🤖 Prompt for AI Agents
In .lsp.json around lines 30 to 37, the language mapping maps ".yml" to "yml"
which is incorrect; update the extensionToLanguage mapping so both ".yaml" and
".yml" map to the VSCode language identifier "yaml" (lowercase) so the
yaml-language-server recognizes .yml files correctly.
|
🎉 This PR is included in version 1.44.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
1 participant
Summary
languageServers→lspServersキーに変更（正しい形式）filetypes→extensionToLanguageマッピングに変更Changes
.claude-plugin/plugin.jsonscript/setup-lsp.sh.devcontainer/devcontainer.jsonnpm/global.json.claude/commands/devcontainer-checklist.mdTest plan
npm run format:check- パスnpm run lint- パスnpm test- 101/101 パスshellcheck script/setup-lsp.sh- パス🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.