Repository navigation
Carry BeatAPI code textures across BeatGeo workspaces - #12
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.
Extend the BeatAPI homepage code texture to BeatGeo’s app shell, setup, sign-in and dark browser workbench while retaining their existing colors. Keep metrics/tables opaque and make textures static, non-interactive and absent from print. Pin the matching BeatBrowser visual update.
A fresh dependency installation exposed missing font declarations in the OG plugin: declare its existing font packages directly so development pages and builds resolve without relying on another workspace’s dependencies.
Validation: authenticated overview, responses and setup rendered at desktop size; setup also checked at 390px with no horizontal overflow. Light and dark previews, login and the dark browser workbench were visually reviewed. No page errors were observed by the browser harness (Vite separately logged a ResizeObserver notification on viewport change). Workspace lint, web types and the production build passed. The paired BeatBrowser passed isolated real extension interaction checks. No new live model collections or billed API calls were made.