Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the comma here cause issues? Aka is there a reason we didn't have it there before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ES5 doesn't allow trailing commas for parameters lists in function calls, that was added in ES6. It's not a problem in browsers, which have moved on from ES5, but for code using requirejs, it'll break deploy (because uglify will fail to parse the file). HQ has been using ES5 in linting rules forever for this reason.
#35651 updated HQ to lint using ES6, now that almost all of our code is off of requirejs. The new lint config expects trailing commas in function calls.
So it should have been there before, I just haven't gotten in the habit yet...that might also be more evidence that I did this file by hand before scripting, since spot checking the related PRs, they have trailing commas for the
hqDefine
callback arguments.