-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for neovim async #99
Comments
I would gladly help in anything you guys need, except scripting. Let me know if you need any help on testing. |
This issue is been tackled on the release 1.x branch and will be closed once vim-prettier 1.0 is released. |
This feature is now available on 1.x release branch |
@FabioAntunes if you have some time could you try out the 1.x release branch ? |
@mitermayer Sorry for the super late response I have been using ALE lately, I will give it a try if you need |
Not a problem! If you have some time please feel to try our 1.x branch as it have neovim support for async already working in there |
I am closing this issue as this is now resolved on 1.x branch |
This issue will be used to track adding support for neovim async, at this moment neovim async is release under a feature flag, however as #96 there are still some bugs that needs to be fixed before the dark feature flag can be removed.
Users that want to experiment with the neovim async and/or want to help tackle this issue can enable it in the meantime by:
While this issue is open the neovim behaviour will keep working as before by defaulting to
sync
0.2.0
The text was updated successfully, but these errors were encountered: