stack/getpaid 2 63 connect and copy - #231
Draft
BullishNode wants to merge 4 commits into
Draft
Conversation
Nothing was ever connected from the merchant's side, so "Reconnect your Bull Bitcoin account" read as though something had broken. State it as the first connection it is, with its own heading above the explanation. The actions under it were a wrapped row of small buttons — a filled Connect beside an outlined Contact support and an outlined Continue with Bitcoin only, reflowing at odd widths. Stack them full-width, one primary and the rest outlined, exactly like the Save and Turn off buttons on the same screen.
…t permission Returning from the Bull Bitcoin login cleared the failure and put the merchant back on the same form. When the login had not produced a scoped settlement credential — what a production account that cannot issue one does every time, and what any server-side issuance failure looks like — the next save failed identically, and the merchant went round again with nothing ever said. Diagnose the round-trip locally instead of assuming it worked, and distinguish the two outcomes: a login that was never completed, and a login that succeeded without granting the settlement permission (where trying again is not the answer, so support is offered). The draft is preserved in both cases, and a credential that did arrive still clears the failure exactly as before.
"Not now (enable later in Backup settings)" put a navigation instruction inside a button label. The button declines the offer; where to change one's mind later is not the button's job.
…reen The page was the old inline "Bull backup" card lifted out of Backup Settings and dropped onto a route: a card inside a page, its own title repeating the page title, a bare switch row, and two half-width Material buttons side by side. Rebuild it in the language of the Backup Settings screen it opens from: the state first, as a label with a coloured on/off value and the single fact that matters under it; a bordered notice, with its own action, when a half-finished recovery needs an answer before anything else; then the toggle and the actions as full-width BBButtons — primary for backing up now, error-outlined for deleting. Behaviour is unchanged: the same enablement rules, the same delete confirmation, the same status and attention lines, driven by the same cubit.
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
2 participants
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.
Stack created with GitHub Stacks CLI • Give Feedback 💬