Disabling nvim async by default under feature flag #98
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
- The new nvim async had some bugs reported, while we are still investigating fixes for it we will then disable it by default, users should be able to still use it by enabling the flag on their .vimrc in the meantime `g:prettier#nvim_unstable_async`
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.
g:prettier#nvim_unstable_asyncIt's important for us to get the neovim integration working, but since there has been some bugs reported on it we need to make sure we mature it a bit more prior to removing the darkfeature flag, users that want to still use neovim async feature can enable it by adding the darkfeature flag
g:prettier#nvim_unstable_asyncto their.vimrcfixes: 96