As of Drupal 8 all JS needs to follow our JavaScript coding standards. For this we use ESLint to check most of our standards.

Here is the summary of running ESLint on this module JS:
✖ 1 problems (1 errors, 0 warnings)

Attached is the full list of errors found by ESLint.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Swetha Yarla created an issue. See original summary.

Swetha Yarla’s picture

FileSize
162 bytes
Swetha Yarla’s picture

Here is the Patch for fixing js errors in Scheduler.

Swetha Yarla’s picture

Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 3: scheduler_vertical_tabs.js_.patch, failed testing.

jonathan1055’s picture

Status: Needs work » Reviewed & tested by the community

Thanks Swetha. I will commit this.

Interestingly, we already had #2490956: Scheduler ESLint errors back in May 2015. At that time, I think this js file did not contain the Use Strict line. I have an archive from Feb 2015 without it, and an archive from June 2015 with it, so it must have been added after those original errors were fixed.

Jonathan

jonathan1055’s picture

Title: Scheduler ESLint errors » Scheduler ESLint errors (part 2)
Status: Reviewed & tested by the community » Fixed
Related issues: +#2490956: Scheduler ESLint errors

Committed. Thank you.

I removed the additional extra blank line at the very end of the file that your patch added. I looked through the JavaScript coding standards you linked, and also the issue about updates for the standards, but did not see anything about requiring a blank line. I checked some core js code files and they did not have it either, so I presumed that was just a mistake in your patch.

pfrenssen’s picture

Assigned: Swetha Yarla » Unassigned

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.