Repository navigation
docs: correct stale in-progress labels for the VS Code and Vim/Neovim extensions - #68
Merged
Merged
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
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.
Summary
While checking what's left on the roadmap, found that DESIGN.md chapter 13's status labels for both editor extensions were stale: "VS Code extension ... in progress" and "Vim/Neovim plugin ... highlighting done, everything past that still open", even though each entry's own body already describes every planned feature as done (folding, jump-to-definition, undefined-variable detection, inline missing/stale/machine indicators for both; Neovim-only for the last two on the Vim side, which need
vim.diagnostic/vim.system). Fixed the two labels to say "done" and note the Neovim-only bit, in both locales.Docs only.
Why?
The headline contradicted its own body and made both extensions look unfinished when they aren't.
Related issue(s)
closes
Check
CONTRIBUTING.md(rules)npm run check(lint & format)npm run typechecknpm run test(functions test)npm run build(dist/)npm run test:coverageand check nothing new went uncovered