Skip to content
This repository was archived by the owner on Feb 4, 2021. It is now read-only.

Conversation

@jezdez
Copy link
Contributor

@jezdez jezdez commented Feb 13, 2018

This adds another Travis environment to install ESLint and run it. Will need to dive into more how ESLint is configured to get this fixed for the Jupyter AMD modules.

@jezdez jezdez requested a review from mdboom February 13, 2018 16:44
Copy link
Contributor

@mdboom mdboom left a comment

Choose a reason for hiding this comment

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

#62 may require redoing some of the actual linting cleanup. Might be less work to finish this after #62 is merged?

@@ -0,0 +1,19 @@
{
"env": {
"browser": true
Copy link
Contributor

Choose a reason for hiding this comment

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

By adding:

"amd": true,
"jquery": true

here, I was able to get this down to only legitimate errors.

  201:21  error  Unexpected console statement                  no-console
  224:31  error  'textStatus' is defined but never used        no-unused-vars
  295:13  error  'nb_path' is assigned a value but never used  no-unused-vars
  341:13  error  'button_td' is not defined                    no-undef
  344:29  error  'button_td' is not defined                    no-undef
  345:24  error  'button_td' is not defined                    no-undef
  352:13  error  'row_message' is not defined                  no-undef
  353:13  error  'row_message' is not defined                  no-undef
  354:24  error  'row_message' is not defined                  no-undef

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Aha, nice, thanks :)

// resource path
"(?:[/?#]\\S*)?" +
"$", "i"
);
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe this improvement to URL validation should be moved to a separate pull request?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, this was totally just to figure out if that gets the number of errors down.

@jezdez
Copy link
Contributor Author

jezdez commented Feb 13, 2018

@mdboom Yeah, that makse sense, just wanted to figure out how this would work with Travis in general, since it by design doesn't support multi-language environments.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants