feat: bracket completion trigger #26
Merged
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
|
Thanks for the PR. I am currently traveling. I will try to review this over the weekend/next week when I get back. |
antonk52
requested changes
May 19, 2024
moliva
force-pushed
the
feat/bracket-completion-trigger
branch
from
1c1774a
to
bd8d3d0
Compare
antonk52
approved these changes
May 21, 2024
|
Thanks! Released in 1.4.0 and published to npm |
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 is an extension to #25.
Introduces
[as a trigger character for completion, managing replacements avoiding to add wrapping characters if already present in file contents (mostly due to automatic edit tools completion).