-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Roadmap v6.0.0 #686
Comments
That seems good to me. |
This has been deprecated for a while. We have decided to remove it entirely for 6.0.0 (jsx-eslint#686). Fixes jsx-eslint#549.
This has been deprecated for a while. We have decided to remove it entirely for 6.0.0 (jsx-eslint#686). Fixes jsx-eslint#549.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#668 and jsx-eslint#686.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#668 and jsx-eslint#686.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#686. Fixes jsx-eslint#668.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#668 and jsx-eslint#686.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#668 and jsx-eslint#686.
This rule is JSX-specific, not React-specific. Changing its name makes this clearer. I've kept the old one around as deprecated. We can remove it at the next major version bump. Addresses jsx-eslint#686. Fixes jsx-eslint#668.
5 down, 4 to go! |
On this roadmap, you have
I'm not entirely sure what you want done here? Does this amount to removing the option and just having it always be the case, or should this be the case by default and there would be a new option like |
I was more thinking about something like this. |
It looks like the last 3 issues all have PRs up - how quickly do you think we could get to a v6? |
@ljharb I hope to publish an RC before friday and the final this week-end if there is no major issue. |
@yannickcr there's still one unchecked item on the list - is that punted to v7? |
I just rebased #699 so it should be able to be merged cleanly. |
@ljharb no, still planned for v6 :) |
Should this be reopened until that's merged? |
Yep |
@yannickcr any more things to add to the above checklist, or are we good for a final release? :-) |
Still a few changes and I think I'll be good to push an RC in the coming hours. |
You can install it with |
I see rc.1 is out. Is there a planned time to release v6? |
What's the timeline on v6.0.0 release? Appears to be blocking airbnb eslint config installation --airbnb/javascript#936 |
@ljharb @nwhitmont |
|
Thanks for all of your hard work on this plugin @yannickcr! This plugin has greatly helped me and my teams over the past couple of years, and I just wanted to make sure you feel appreciated for the effort you put in here. This is such an valuable tool that you've built. 👏 👏 👏 Thinking ahead to future major version bumps, I'm wondering--is there anything that I (or others who are interested) can do to help make sure that things continue to run smoothly? I don't want you to feel like you are running this thing all by yourself. |
Thank you @yannickcr ! |
Thank you all for your support 😍 , and thanks for your contributions @lencioni 😃
Well, there is more and more open issues and PRs to review/validate and I have some difficulties to keep up with all of this. I added @ljharb as a contributor a few months ago and he made a really great work on issues triage, PRs validation and responding to users questions ❤️ . So I'm now thinking about adding more people as contributors. Would you be interested to be added as contributor @lencioni? |
I'm biased because I work with @lencioni, but I highly endorse his being added! |
Sure! |
Done :) |
So here's what I have in mind for now:
all
configuration (Enable all rules #674, PR Add in an "all" config #683)jsx-sort-prop-types
rule (Remove deprecated jsx-sort-prop-types rule? #549)jsx-
prefix (keep old rules with a warning likejsx-sort-prop-types
) (Rename some JSX-specific rules to include "jsx-" prefix #668, PR Rename some JSX-specific rules to include jsx- prefix #689)findDOMNode()
warning rule (Rule proposal: warn against using findDOMNode() #678)allow-in-func
mode by default inno-did-mount-set-state
andno-did-update-set-state
rules (PR Enable allow-in-func mode by default in no-did-mount-set-state and no-did-update-set-state rules #702)recommended
configuration discussions and update it accordingly (PR Remove no-danger from recommended rules #636, consider removing no-did-mount-set-state from recommended rules #596)Do you see anything else that could be good to change/improve?
The text was updated successfully, but these errors were encountered: