Skip to content

Conversation

@saschanaz
Copy link
Member

@saschanaz saschanaz commented Jun 10, 2018

Config file generated by npx eslint --init.

Closes #167

"mocha": true
},
"extends": "eslint:recommended",
"rules": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that we are extending “eslint:recommended”, it possible to only list the ones we are changing?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the generated one is more strict, as eslint --init reads our existing code to get an optimized configuration. For example, array-callback-return is not enabled by default in eslint:recommended.

Copy link
Member Author

@saschanaz saschanaz Jun 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may still review those off things, though.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it seems we can just remove those off lines, but IMO maybe those lines are helpful for future reconsideration (at least we know they exist!). Should they be removed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t mind keeping it as is, but I’m worried that we don’t know which are set by us or why - and the recommended set can change or have new things added. I guess it’s not a big deal as the code base is only small.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m worried that we don’t know which are set by us or why

We have rules list and their detailed descriptions and examples, so maybe we can further modify the configuration if we meet some problems.

I'm hesitating to just remove them, as some actually are helpful... 636947f

@saschanaz
Copy link
Member Author

Replaced by #202

@saschanaz saschanaz closed this Jun 12, 2018
@saschanaz saschanaz deleted the eslint branch June 12, 2018 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants