-
-
Notifications
You must be signed in to change notification settings - Fork 681
ETA / roadmap / remaining issues for v7 #1176
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
Comments
Thank you for your question. I'm glad to know that you're looking forward to it. I have the following plans for v7.
These plans are subject to change. Thank you for your understanding. |
Thanks for the swift response. I don't have intention of upgrading my project to Vue3 anytime soon. I mention that because, if the main issues left are Vue3 related, maybe the best thing I can do now is upgrade to the latest alpha and do some testing to see if I get any issues. I'll give that a go and let you know how it goes next week. In the meantime, feel free to close this issue if you wish. |
ESLint landed optional chaning support in v7.5.0 on July 18th and nullish coalescing was released in v7.2.0 on June 5th. Both of these happened after this plugin released ESLint 7 support (in version v7.0.0-alpha.2 on May 10th) so I wanted to let you know in case you weren't yet aware. As far as I know that means @ota-meshi all of the criteria is met for a new major release for this plugin. My apologies if there's somewhere else where the status of a release is discussed but I haven't yet seen it if such a place exists. |
I just released v7🚀 |
I'm looking forward to release v7 for a few new rules that I have my eye on, but I'm refraining from upgrading now because I'd like to wait for v7 to be released as stable.
For this reason, I'm wondering whether there is a list of remaining issues somewhere that I can possibly give a hand with to accelerate the release?
I'm guessing that maybe creating a new v7 milestone might be the easiest way to solve this for everyone in my situation.
The text was updated successfully, but these errors were encountered: