fix: yaml-ls initialization and bootstrap environment issues #6986
+25
−32
Conversation
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
Contributor
|
The following comment was made by an LLM, it may be inaccurate: Duplicate Check ResultsNo duplicate PRs found. All searches returned only PR #6986 (the current PR), indicating that there are no other open or recently-merged PRs addressing:
This appears to be the first PR tackling these yaml-ls and environment stability issues. |
processtrader
force-pushed
the
fix-yaml-ls-and-bootstrap
branch
2 times, most recently
from
71a5237 to
b514df7
Compare
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
Author
Issue #7842 |
processtrader
force-pushed
the
fix-yaml-ls-and-bootstrap
branch
from
b514df7 to
e1d22ad
Compare
Contributor
Author
|
@rekram1-node any chance to consider this as valid/useful? thanks! |
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
This PR fixes the
yaml-lslanguage server which was failing to initialize due to incorrect executable paths and restrictive root detection.Changes
YAML LSP (
yaml-ls)bun x yaml-language-server --stdio. This ensures the server works reliably by using the package manager to resolve the binary, avoiding "file not found" errors caused by version-specific path changes innode_modules..yamllint,kustomization.yaml,docker-compose.yaml) to correctly identify workspace roots in non-Node.js projects.completion,hover,validation, andschemaStoreby default in the server initialization options.Verification
yaml-lsnow correctly identifies syntax errors and provides schema-based diagnostics.bun x.Issue: #7842
With the changes, meaning, LSP working:
Latest OpenCode 1.1.14:
Adding again a new key, with the fix applied: