Skip to content

Eslint update (part 3) - #2913

Open
MomoRazor wants to merge 11 commits into
masterfrom
eslint-update-2-3
Open

MomoRazor wants to merge 11 commits into
masterfrom
eslint-update-2-3

Conversation

@MomoRazor

Copy link
Copy Markdown
Contributor

This updates focused on refactoring the following sections (for Eslint purposes):

  • BoxReconciliationAccordion
  • The Match Products and Receive Location Forms
  • The Walkthrough and Tour features
  • BoxView, AddItemsToBoxOverlay and TakeItemsFromBoxOverlay sections
  • Shipment Content and Export Buttons

There are also the changes included in the type-fixes branch, however these should be merged first I believe.

Do let me know if we'd prefer to split this up further @pylipp! Thanks!

@codecov

codecov Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.22%. Comparing base (bf1c410) to head (49fd810).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2913      +/-   ##
==========================================
- Coverage   74.24%   74.22%   -0.02%     
==========================================
  Files         332      332              
  Lines       25459    25449      -10     
  Branches     2537     2537              
==========================================
- Hits        18902    18890      -12     
- Misses       6507     6509       +2     
  Partials       50       50              
Flag Coverage Δ
backend 99.65% <ø> (ø)
frontend 66.78% <ø> (-0.03%) ⬇️
sharedComponents 44.29% <ø> (ø)
sharedFront 91.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

}
}
} catch (err) {
console.error(err);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Deliberate console?

: false;

useEffect(() => {
setCurrentState(boxData?.state);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

well-spotted clean-up!

clearTimeout(t);
setRun(false); // Clean up state when component unmounts or path changes
};
}, [isActive]); // Only depend on isActive starting/stopping

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Without the activePath dependency and without setStepIndex(0), the following happens:

  1. log in as coordinator
  2. open the walkthrough
  3. select first path
  4. forward until step 3
  5. in the top right corner, select path 2 from the dropdown
  6. Observed: path 2 opens but the tooltip is squeezed into the top left corner, not highlighting the actual menu item. Also it shows step 3, not step 1. Expected: the tooltip correctly highlights the Dashboard menu item (step 1 for path 2)

@pylipp pylipp left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MomoRazor thanks for the valuable clean-up!
There's still a small regression with resetting the step index In the walkthrough tour.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants