Repository navigation
Rebuild Explorer with Bloom dashboards and responsive detail panes - #30
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.
Explorer now uses Bloom's dashboard and split-pane APIs throughout the app. Blocks and transactions open beside the originating screen on desktop and slide between panes on mobile, preserving filters and document scroll. The main screen is a ContentPanel from its first render.
The migration removes the local UI adapter layer, consolidates the Bloom provider and FairCoin theme, and replaces duplicate status, form, code and pagination UI. Charts use all 21 chart-card families with real source data and rows that adapt to the available panel width. First-paint theme initialization and production CSP hashes agree.
Bloom's pane-motion implementation is tracked upstream in OxyHQ/Bloom#270. This app pins the verified local package and source patch under vendor/ until a registry release includes that API; it does not depend on an external checkout. New analytics strings are translated in English and Spanish; the remaining catalogs retain the existing English fallback convention.
Validation: frontend/server typecheck, 122 tests, production build, all 17 locale catalogs have matching keys. Browser checks cover desktop/mobile pane movement, route and scroll restoration, reduced motion, five chart widths, first-paint light/dark themes with CSP, forms, and real block/transaction/address content. Production build retains Vite's large-chunk warning.