Closed ascott1 closed 9 years ago
Before merging, it may be worth ripping out all of the custom JSHint comments throughout the code as well.
I think this should be merge ready now!
Looks good, I'm going to run it to test before merging.
Sounds like a plan!
Relatedly, I opened up this issue to create a standardized ESLint file across projects. Once we've reached a consensus, we can make sure out stuff conforms.
This sets up ESLint in place of JSHint and adds the appropriate grunt task. I've disabled all of the current failures (since they were passing the JSHint file), but it may be worth going through and systematically fixing many of them or consciously choosing to ignore the suggestion.
Note: Let's wait to merge until after the front end team discusses the us of ESLint this afternoon.