Bring scripts and autocomplete data into main repository #6
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
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.
There's not much to be done to incorporate these completions, so rather than trying to move my function in and remove all the fuzzy matching I'm just going to bring my parsing scripts across so you can use them and so I can synchronize my repo and make pull requests directly rather than through mcepl's repo.
I've added my scripts, the spec.md I'm working from, and the output I've got so far to the utils directory, along with a brief README.rst.
The autocomplete_data.json file is just an array of two-element arrays in the form [[keyword, documentation], ...] that are easy to map to
labelanddocumentationin CompletionItem.So far this covers all the various preamble and dependencies keywords as well as a sizeable chunk of the scriptlets.