Restore Topgear profile and payments menu links - #417
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
On the Topgear hosts, the signed-in avatar menu now restores community-app’s Wipro destinations: My Profile opens
https://topgear-app.wipro.com/user-details, and Payments openshttps://topgear-app.wipro.com/my_paymentsin a new tab. Account Settings and Log Out remain available.The links are scoped to exactly
topgear.topcoder.comandtopgear.topcoder-dev.comusing the header’s existing host selector. Other hosts retain their Topcoder profile destination and existing menu.Validation:
npm run lint,npm test, andnpm run buildpass. Built-bundle browser checks cover both Topgear hosts, desktop/mobile menus, and the unchanged Platform UI host menu.The navigation bundle is published to dev, its served bytes match the local build, and its CloudFront invalidation completed. Browser checks against the deployed Platform UI with controlled signed-in profile/membership responses confirm both legacy destinations on desktop and mobile. Companion access gate: topcoder-platform/platform-ui#2427.
CI build, type checks, and CodeQL pass. The existing Trivy workflow cannot start because
aquasecurity/trivy-action@0.33.1does not resolve; this change does not modify that workflow.