init-options: support initialization options in .JETLSConfig.toml#398
Merged
init-options: support initialization options in .JETLSConfig.toml#398
Conversation
Initialization options can now be configured via the `[initialization_options]` section in `.JETLSConfig.toml`, in addition to editor-specific LSP settings. This provides a client-agnostic way to configure initialization options that can be committed to version control. When both sources are present, file-based configuration takes precedence (file > client > default), as like the dynamic configuration. But I may revise this priority rule in the very near future.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #398 +/- ##
==========================================
- Coverage 65.24% 65.23% -0.01%
==========================================
Files 44 44
Lines 4975 4991 +16
==========================================
+ Hits 3246 3256 +10
- Misses 1729 1735 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Initialization options can now be configured via the
[initialization_options]section in.JETLSConfig.toml, in addition to editor-specific LSP settings. This provides a client-agnostic way to configure initialization options that can be committed to version control.When both sources are present, file-based configuration takes precedence (file > client > default), as like the dynamic configuration. But I may revise this priority rule in the very near future.