Skip to content

Conversation

@codemist
Copy link
Collaborator

@codemist codemist commented Oct 16, 2025

References:

Jira: MNTOR-5033
Figma:

Description

Screenshot (if applicable)

Not applicable.

How to test

Checklist (Definition of Done)

  • Localization strings (if needed) have been added.
  • Commits in this PR are minimal and have descriptive commit messages.
  • I've added or updated the relevant sections in readme and/or code comments
  • I've added a unit test to test for potential regressions of this bug.
  • If this PR implements a feature flag or experimentation, I've checked that it still works with the flag both on, and with the flag off.
  • If this PR implements a feature flag or experimentation, the Ship Behind Feature Flag status in Jira has been set
  • Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.
  • All acceptance criteria are met.
  • Jira ticket has been updated (if needed) to match changes made during the development process.
  • Jira ticket has been updated (if needed) with suggestions for QA when this PR is deployed to stage.

return (
<div
/* c8 ignore next */
className={`${styles.container} ${props.variant ? styles[props.variant] : ""}`}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Never had to write a unit test here before, not sure why it's acting up now.

Copy link
Collaborator

Choose a reason for hiding this comment

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

That's because the component was removed from SettingsContent, which appears to be the only place the variant prop was used. I think that's a sign to remove the whole variant code (i.e. the .secondary class and the references in here), instead of adding the c8 ignore.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

You're right - that variant wasn't being used anywhere. Remove the prop and condition in 6bfc7a3, thank you!

Copy link
Collaborator

@Vinnl Vinnl left a comment

Choose a reason for hiding this comment

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

Well underway, but there are a couple more cleanup chores that need to happen, I think.

@codemist codemist requested a review from Vinnl November 6, 2025 15:29
Copy link
Collaborator

@Vinnl Vinnl left a comment

Choose a reason for hiding this comment

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

There are still a bunch of open questions and cleanup tasks from my previous review that I think you might've missed?

case "manage-account":
return <SettingsPanelManageAccount {...props} />;
case "edit-profile":
if (props.enabledFeatureFlags.includes("EditScanProfileDetails")) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

This appears to be removing a different feature flag?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oops you're right, that was me trying to test something. Reverting in 07200db

Comment on lines 116 to 117
it("changes the active tab", async () => {
const user = userEvent.setup();
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this old UI that no longer exists?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This test was for the deprecated sidebar navigation, which is being removed in this PR. Its removal doesn’t affect Jest coverage, so it’s no longer needed.

/* c8 ignore next */
className={`${styles.toolbar} ${props.enabledFeatureFlags.includes("SidebarNavigationRedesign") ? styles.hasBackground : ""}`}
>
<nav className={`${styles.toolbar} ${styles.hasBackground}`}>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we now remove the .hasBackground class and just roll those styles into .toolbar?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed in 51c6618

@codemist
Copy link
Collaborator Author

@Vinnl Sorry it took me a while to get back to this. All of your comments should have been addressed now - let me know if you need me to walk you through it.

@codemist codemist requested a review from Vinnl November 20, 2025 15:17
* MNTOR-4178 - Remove EditScanProfileDetails feature flag

* update basetest

* fix build errors

* pass empty feature flag array to settings wrapper

* Remove EditScanProfileDetails flag logic and restore FreeOnly branching for Edit Info nav link

* add tests
@codemist codemist marked this pull request as draft November 21, 2025 18:04
@Vinnl
Copy link
Collaborator

Vinnl commented Nov 24, 2025

@codemist Sorry, now I didn't get around to it due to the shutdown timecrunch. I see you just marked this as draft, I assume that's because of the in-progress merge? Do you need help with that?

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.

3 participants