Skip to content

Lint code using eslint instead of jshint #72

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
merged 1 commit into from
Jun 16, 2017
Merged

Lint code using eslint instead of jshint #72

merged 1 commit into from
Jun 16, 2017

Conversation

manicki
Copy link
Member

@manicki manicki commented Jun 1, 2017

@thiemowmde
Copy link
Contributor

Travis still iterates into the node_modules/… directory and complains. Do you know how to fix this?

@manicki
Copy link
Member Author

manicki commented Jun 1, 2017

I have no idea ATM. Didn't happen for me locally, I am not sure what did I mess up.

@Ladsgroup
Copy link
Contributor

It says it can not install eslint now: https://travis-ci.org/wmde/WikibaseDataModelJavaScript/builds/238402279

@manicki manicki force-pushed the eslint branch 3 times, most recently from abe10a6 to 3d2ec30 Compare June 7, 2017 15:14
@manicki
Copy link
Member Author

manicki commented Jun 7, 2017

OK, it was failing because it is build as a PHP project, and PHP VMs have an old node version which is incompatible with eslint version used.
After several attempts I managed to get this work. It is is a bit hacky and rather fragile. OTOH I believe I understand the reason behind distributing a JS library as as package on packagist. Hopefully one day this all will be installed with npm and so on.

@JeroenDeDauw
Copy link
Contributor

distributing a JS library as as package on packagist

The way it's written it's a MW extension, not a JS lib

@manicki
Copy link
Member Author

manicki commented Jun 8, 2017

oh, of course. Silly me.
Then I guess having a PHP build with installing new-enough node is probably the best we can get for now.

@thiemowmde
Copy link
Contributor

Do you think this is fine to be merged as it is now? Looks fine for me. Is there something we can improve about the "fragile" bits you mentioned?

@manicki
Copy link
Member Author

manicki commented Jun 16, 2017

Do you think this is fine to be merged as it is now?

Yes.

Is there something we can improve about the "fragile" bits you mentioned?

Nothing particular I can think of now.

@thiemowmde thiemowmde merged commit 35e4cbb into master Jun 16, 2017
@thiemowmde thiemowmde deleted the eslint branch June 16, 2017 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants