Skip to content
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

MNTOR-3378 - Data broker manual removal 🔴 DO NOT MERGE - Waiting for regression testing 🔴 #5287

Open
wants to merge 61 commits into
base: main
Choose a base branch
from

Conversation

codemist
Copy link
Collaborator

@codemist codemist commented Nov 4, 2024

References:

Jira: MNTOR-3378
Figma: https://www.figma.com/design/DTbmXzCQCw2PxXpHQW8yfW/Monitor-MVP-Enhancements?node-id=3809-6501&t=EniBV7WqvPVnuivk-4

Path: /user/dashboard/fix/data-broker-profiles/removal-under-maintenance

Description

Screenshot (if applicable)

image image image

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, 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.

Copy link

github-actions bot commented Nov 4, 2024

Comment on lines +11 to +12
| "removed"
| "removal_under_maintenance";
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@rhelmer I believe this would be our first time consuming this endpoint for the manual data broker removal feature.

@codemist codemist requested a review from rhelmer November 4, 2024 19:20
Copy link

github-actions bot commented Nov 4, 2024

Copy link

github-actions bot commented Nov 4, 2024

Copy link

github-actions bot commented Nov 6, 2024

@codemist codemist marked this pull request as ready for review November 12, 2024 18:53
@codemist codemist added the 🛑 Do Not Merge Do not merge this PR, even if approved. label Nov 12, 2024
Copy link

@codemist
Copy link
Collaborator Author

Fixed that linter error here 32831a1 @flozia

Copy link
Collaborator

@flozia flozia left a comment

Choose a reason for hiding this comment

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

Thanks for addressing my previous comments and making all the updates after aligning with UX!

I’m already submitting my “in progress” review to not block you waiting on reviews. At the moment I’m not able to access all views and test the functionality fully. I’m having issues to access the page /user/dashboard/fix/data-broker-profiles/removal-under-maintenance. I’ve tried adding mock broker results and also modifying the query in getScanResultsWithBrokerUnderMaintenance to get results back. Could you update the description with some guidance on how to test this best?

@codemist
Copy link
Collaborator Author

@flozia You should only be seeing a list if you're premium.

@codemist codemist added 🛑 Do Not Merge Do not merge this PR, even if approved. and removed 🛑 Do Not Merge Do not merge this PR, even if approved. labels Nov 27, 2024
@codemist codemist changed the title MNTOR-3378 - Data broker manual removal MNTOR-3378 - Data broker manual removal 🔴 DO NOT MERGE - Waiting for regression testing 🔴 Nov 27, 2024
Comment on lines +26 to +28
if (!session?.user?.subscriber?.id || !hasPremium(session.user)) {
redirect("/user/dashboard");
}
Copy link
Collaborator Author

@codemist codemist Nov 28, 2024

Choose a reason for hiding this comment

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

This feature should only be available to Plus users - I also added this logic in isEligibleForStep in getRelevantGuidedSteps.ts.

Comment on lines +114 to +119
<div className={`${styles.ldsRing} ${variant ? styles[variant] : ""}`}>
<VisuallyHidden>{l10n.getString("loading-accessibility")}</VisuallyHidden>
<div></div>
<div></div>
<div></div>
<div></div>
<div className={variant ? styles[variant] : ""}></div>
<div className={variant ? styles[variant] : ""}></div>
<div className={variant ? styles[variant] : ""}></div>
<div className={variant ? styles[variant] : ""}></div>
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added this here to style the fill colour of the loading ring depending on the button variant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛑 Do Not Merge Do not merge this PR, even if approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants