Add sourcekitten completion results formatting options #712
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
PaulTaykalo
force-pushed
the
improvement/format-output
branch
from
92fcdd2 to
d44cb63
Compare
|
This is open question whether to make these options available at all, or what options should be by default. If you have some other thoughts on that I would gladly rewrite this PR :) or even close it:) |
|
changelog entry: febae1a |
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.
Since JSON-formatting of code completion results can take a lot of time in some cases, additional format options can be passed to the sourcekitten.
Two additional options added:
prettified- whether JSON results should be user-friendly prettifiedsorted-keys- whether the keys in JSON should be sorted keysThis fixes #710