Skip to content
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 v4.0.0 #436

Closed
7 tasks done
yannickcr opened this issue Feb 9, 2016 · 11 comments
Closed
7 tasks done

Roadmap v4.0.0 #436

yannickcr opened this issue Feb 9, 2016 · 11 comments

Comments

@yannickcr
Copy link
Member

There is a few things that I'd like to changes for a while (default configuration changes, rules renaming/suppression and a few others) and with the upcoming ESLint v2.0.0 release I think it is the right time to do this.

So here's what I have in mind for now:

Do you see anything else that could be good to change/improve?

@ljharb
Copy link
Member

ljharb commented Feb 12, 2016

v2.0.0 is now released - time to get that out ASAP :-D

@yannickcr
Copy link
Member Author

It's should be done during this week-end :)

lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Feb 13, 2016
This was a change that has been queued for v4.

Addresses jsx-eslint#436
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Feb 13, 2016
This was a change that has been queued for v4.

Addresses jsx-eslint#436
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Feb 13, 2016
This was a change that has been queued for v4. I considered changing the
default from false to true, but I think it makes more sense to invert
the option to be an ignore option.

Addresses jsx-eslint#436
@yannickcr
Copy link
Member Author

Just published 4.0.0-rc.0 on npm, you can test it by running:

$ npm install eslint-plugin-react@next

Let me know if you find any issue or if you have suggestions about the new recommended configuration.

@lukekarrys
Copy link
Contributor

Thanks @yannickcr. v4 looks pretty good to me.

I did find one bug that I opened here: #443. I think it is due to b2661aa, but I'm not sure how to differentiate stateless component functions from other functions with destructured arguments.

@yannickcr
Copy link
Member Author

Thanks @lukekarrys, the issue should be fixed in 6643f87.

I will publish another RC tomorrow.

@yannickcr
Copy link
Member Author

Just published 4.0.0-rc.1 on npm.

@lukekarrys
Copy link
Contributor

Thanks @yannickcr. I'm using rc.1 across three different projects now with no issues 😄

@Lysholm
Copy link

Lysholm commented Feb 18, 2016

Thanks @yannickcr! Seconding @lukekarrys sentiment, no problems with rc.1 in my two projects.

@yannickcr
Copy link
Member Author

Happy to hear it! In this case, I think I will publish 4.0.0 tomorrow (same as rc.1 with a few documentation fixes).

@diorahman
Copy link

Nice!

@yannickcr
Copy link
Member Author

4.0.0 is now published

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants