Add host-scoped Topgear community header - #416
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.
Topgear members need the community header when the host moves from community-app to Platform UI. Tool navigation now automatically renders the Wipro, Topcoder, and Topgear logos on exactly
topgear.topcoder.comandtopgear.topcoder-dev.com; integrations may also requesttype: 'topgear'.Home links to
https://topgear-app.wipro.com, and Challenges links to/opportunities/challengeon the current Topgear origin. The responsive header retains account controls and omits Leaderboard and the tool selector. Other hosts keep the standard navigation. The CORS template includes both environment-specific Topgear origins.Validation:
npm run lint,npm test, and the full build pass. Browser checks passed on both Topgear hosts at 1440, 768, 375, and 320 pixels, and confirmed the standard header on the Platform UI host. Added a lint script using the existing Svelte check and corrected three existing nudge type annotations so it passes.Companion Platform UI PR #2426 removes the hero banner and adds the dev-only legacy URL redirect. Production routing remains unchanged. Base is
devas confirmed; this repository has nodevelopbranch.Dev deployment verified on 2026-10-02 (Australia/Hobart): the live navigation bundle matches the built artifact, CORS allows the Topgear dev origin, and the full Platform UI page renders all three logos with readable mobile branding at 375 and 320 pixels. No production bundle or routing was deployed.
CI build and type checks pass. The pre-existing Trivy workflow fails before scanning because
aquasecurity/trivy-action@0.33.1cannot be resolved; the workflow is unchanged by this PR.