(DO NOT MERGE)feat: console widget - #314
Conversation
…entry The console becomes a my-account area: a dedicated layout with its own top bar (chain switcher and wallet chip in the header, matching the explorer's selector position), beta banner, and sidebar sections for Dashboard, Authorizations, and Alerts. The explorer header replaces the Console tab with a Connect Wallet / address-chip entry point. Explorer routes move into a route group that owns the navigation chrome, removing the useShowNetworkOptions pathname hack.
Leads the network home page with a console entry hero (eyebrow, heading, single Open Console action) above the search bar and stats, so console access is discoverable from page content as well as the header.
The explorer URL, the shared network context, and the wallet chain previously drifted apart when moving between the explorer and the console. Now an explicit selection is tracked in the network context: deep links still adopt the URL's network, but once a selection exists a stale URL (e.g. reached with the browser back button) is rewritten to the selection instead of clobbering it. Entering the console with a wallet on a different chain asks the wallet once to follow the selection; afterwards the wallet chain is the source of truth and the context follows it. The console header keeps a network selector while disconnected, driving the context directly.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Happy to take a look. I’m not quite sure what the expected outcome/scope of this PR is beyond the two points above. Could we clarify that before I take it over and start making changes? |
It’s exactly what the PR description says, nothing more; I believe it already implemented expected outcomes (as shown in demo) |
There was a problem hiding this comment.
I like the banner in the app, but I don't think the Explorer should have the wallet connect component. The Explorer shows chain data and general metrics that aren't tied to the user's wallet, and connecting a wallet doesn't change anything there. Having this component could make users think it affects what they're seeing somehow.
I think keeping a clear separation between the Explorer and the Console makes the purpose of each one clearer.
If you want i can add the banner to my console redesign poc PR. Or you can just change the target branch to mine and add it there, since there's already some overlap between the two.
|
aligned with @BravoNatalie on the suggested changes, and she is going to pull the console widget into her branch for the usage PR, expecting that PR supercede this! |
|
The ConsoleHero was added in this PR #338 |
5 participants
Review note: