-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
[JENKINS-68904] Adress ESLint violations #6794
Conversation
The failure can be seen on https://ci.jenkins.io/job/Core/job/jenkins/job/PR-6794/2/consoleFull and has been reverted by now. |
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.
commit 6b70fc8 is not fully reverted by commit f40fca8. I would prefer that it be fully reverted and that we discuss the topic of enforcement in a separate PR (the fix for JENKINS-68903), since there are multiple ways to implement JENKINS-68903 and the partial revert in f40fca8 implements the solution to JENKINS-68903 that I describe in that bug as "less attractive."
@@ -330,7 +331,7 @@ function checkRowCellOverflows(row) { | |||
// build name (first field) a block element, forcing the details and controls to wrap | |||
// onto the next row (creating a second row). | |||
buildName.classList.add('block'); | |||
var wrap = blockWrap(buildDetails, buildControls); | |||
wrap = blockWrap(buildDetails, buildControls); |
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.
Ah yes, the intricacies of variable scope in JavaScript… 😄 I don't understand this but I trust you.
buildBadge = $(buildControls).getElementsBySelector('.build-badge')[0]; | ||
if (buildBadge) { | ||
var badgeOverflowParams = getElementOverflowParams(buildBadge); | ||
badgeOverflowParams = getElementOverflowParams(buildBadge); |
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.
Ah yes, the intricacies of variable scope in JavaScript… 😄 I don't understand this but I trust you.
The commit has been reverted properly 👍🏻 |
This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process. Thanks! |
Addresses the ESLint part of JENKINS-68904
The latest commit simulates a CI failure and will be reverted once demonstrated.
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
Proposed changelog entries
section only if there are breaking changes or other changes which may require extra steps from users during the upgrade@Restricted
or have@since TODO
Javadoc, as appropriate.@Deprecated(since = "TODO")
or@Deprecated(forRemoval = true, since = "TODO")
if applicable.Desired reviewers
@mention
Maintainer checklist
Before the changes are marked as
ready-for-merge
:Proposed changelog entries
are accurate, human-readable, and in the imperative moodupgrade-guide-needed
label is set and there is aProposed upgrade guidelines
section in the PR title. (example)lts-candidate
to be considered (see query).