Refine and distribute yang-lsp-settings-schema.json #238
Conversation
This file contains 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
esmasth
force-pushed
the
esmasth/issue233
branch
3 times, most recently
from
eed7fc7
to
2d4bf01
Compare
Also modularize editorconfig settings This change relates to TypeFox#233 Signed-off-by: Siddharth Sharma <[email protected]>
Also - added markdownDescription statements to json schema - modularized editorconfig settings, and added more files - resolved markdownlint warnings This change relates to TypeFox#233 Signed-off-by: Siddharth Sharma <[email protected]>
esmasth
force-pushed
the
esmasth/issue233
branch
from
2d4bf01
to
7814a29
Compare
|
@dhuebner request your review here. This should be the last for the associated issue. |
|
@esmasth |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This will allow for YANG LSP client implementations to apply the precise version of the schema matching the lifecycle of the server.
This relates to #233