You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
authored
chore(ui): remove the superseded standalone identities screen (#971)
The Identity Hub covers everything the standalone identities list did, and
the nav has not offered a way to reach that list for some time. Four live
controls still routed to it, though, and `set_main_screen` persists the
choice — so finishing a wallet import and choosing "Create Identity" parked
the user on a screen with nothing highlighted in the nav, there and on every
later launch. Those controls now point at the hub, and the screen is gone.
Rerouted to `RootScreenIdentityHub`: "Create Platform Identity" after wallet
creation, "Create Identity" / "Load Existing Identity" on the import success
screen, "Register DPNS Name" on the add-identity success screen, and the
Register-DPNS breadcrumb. The seven `add_left_panel` arguments that named the
retired route highlighted nothing; they now name the hub, matching what
`keys_screen` already did.
Encoding 0 is retired and decodes to `None`, so a returning user's persisted
value falls through to the settings default. That default was DashPay, which
is itself absent from the nav — it becomes the hub, matching
`app::FALLBACK_ROOT_SCREEN`, under a regression test.
`OnboardingAction::ImportIdentity` is dropped: it is absent from
`ONBOARDING_CARDS` and constructed nowhere.
The `nav_button_specs` doc claimed the retired routes stayed reachable via
deep links and MCP tools. Neither exists: there is no URI handler anywhere,
and `src/mcp/` and `src/bin/` reference no UI screen type.
The deleted kittest file's three app-shell tests move to `startup.rs`; a
fourth duplicated `startup::test_app_startup`. Its two Keys-popup regressions
are already covered on the live path by `keys_screen.rs` and at model level
in `encrypted_key_storage.rs`.
Co-authored-by: Lukasz Klimek <842586+lklimek@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/user-stories.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -814,7 +814,7 @@ As a masternode operator, I want my previously scheduled DPNS votes to survive a
814
814
815
815
As a user who has requested a username that is not yet awarded, I want to see that the request is pending so that I am not told to "pick a username" for a name I have already chosen.
816
816
817
-
- A requested-but-unawarded name shows a "Pending" pill next to the identity — on both the Identities list and the Identity Home hero card.
817
+
- A requested-but-unawarded name shows a "Pending" pill next to the identity — on both the Identity Home hero card and the Identity Settings tab.
818
818
- The hero card shows the requested name with the pill instead of the "No username yet — Pick a username" prompt.
819
819
- The onboarding checklist counts the submitted request as completing "Pick a username" while clearly stating that Dash masternodes are voting.
820
820
- The pill's tooltip explains that Dash masternodes decide who receives the username and, when the decision time is known, gives an estimated decision time.
0 commit comments