So here's what I have in mind for now:
all configuration (#674, PR #683)jsx-sort-prop-types rule (#549)jsx- prefix (keep old rules with a warning like jsx-sort-prop-types) (#668, PR #689)findDOMNode() warning rule (#678)allow-in-func mode by default in no-did-mount-set-state and no-did-update-set-state rules (PR #702)recommended configuration discussions and update it accordingly (PR #636, #596)Do you see anything else that could be good to change/improve?
That seems good to me.
5 down, 4 to go!
On this roadmap, you have
Enable allow-in-func mode by default in no-did-mount-set-state and no-did-update-set-state rules
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 disallow-in-func?
should this be the case by default and there would be a new option like
disallow-in-func
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.
v6.0.0-rc.0 is now published on npm.
You can install it with npm install eslint-plugin-react@next
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 --https://github.com/airbnb/javascript/issues/936
@ljharb @nwhitmont v6.0.0 should be released in the coming hours.
v6.0.0 is now published on npm
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 馃槂
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.
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!
Would you be interested to be added as contributor @lencioni?
Sure!
Done :)
Most helpful comment
@ljharb I hope to publish an RC before friday and the final this week-end if there is no major issue.