Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Migrate linting from standard to XO #53

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

Merged
leo merged 1 commit into vercel:master from jfmengels:xo
Oct 15, 2016
Merged

Migrate linting from standard to XO #53

leo merged 1 commit into vercel:master from jfmengels:xo
Oct 15, 2016

Conversation

@jfmengels
Copy link
Contributor

@jfmengels jfmengels commented Oct 15, 2016

Migrate linting from standard to XO, to have a consistent linter and style accross the Zeit projects, as requested by @leo.

Notes:

  • I also added 'xo's react config for this project.
  • There are two proptypes that seem to not be used explicitly. From what I gather, they are accessed and used dynamically, so I ignored the warnings there.

Copy link
Contributor

leo commented Oct 15, 2016

Thanks! But why do we need to use babel-eslint as a parser? Isn't esnext: true enough?

Copy link
Contributor Author

xo supports jsx syntax out of the box, but you need babel-eslint to support not-yet standard features. In this case, you're using static class properties, which is not yet supported by the default parser.

Copy link
Contributor

leo commented Oct 15, 2016

Ahhhh. Thanks! 😊

@leo leo merged commit 40e1aa9 into vercel:master Oct 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /