Skip to content

Comments

add a design doc for new transaction flow#1900

Open
jeesunikim wants to merge 4 commits intomainfrom
doc-new-tx-flow
Open

add a design doc for new transaction flow#1900
jeesunikim wants to merge 4 commits intomainfrom
doc-new-tx-flow

Conversation

@jeesunikim
Copy link
Contributor

@jeesunikim jeesunikim commented Feb 23, 2026

Copilot AI review requested due to automatic review settings February 23, 2026 19:00
@github-project-automation github-project-automation bot moved this to Backlog (Not Ready) in DevX Feb 23, 2026
@stellar-jenkins
Copy link

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a detailed design/implementation document describing a redesigned single-page transaction flow (Build/Simulate/Sign/Submit) and Soroban auth entry signing during simulation.

Changes:

  • Document single-page stepper-based transaction flow with shared-link behavior and legacy route redirects.
  • Specify planned components/state management for Build/Simulate/Sign/Submit, including Soroban-only Simulate step.
  • Describe Soroban auth-entry signing UI/flow and related store/helpers/components.
Comments suppressed due to low confidence (3)

docs/new-transaction-flow.md:500

  • Within the ASCII diagram, a few border lines end with a literal hyphen (e.g. └──────────────────────────────-┘, └───────────────────────────────-┘), which looks like a typo and breaks the box drawing alignment in many renderers. Replace the trailing - with the matching box-drawing character () so the diagram renders cleanly.
│                          │ └──────────────────────────────-┘ │  │
│                          │                                    │  │
│                          │ ┌ Simulated Result ─────────────┐ │  │
│                          │ │ JSON code viewer (RPC response)│ │  │
│                          │ └───────────────────────────────-┘ │  │

docs/new-transaction-flow.md:261

  • ClassicOperation.tsx:544 is referenced as a line-number citation. Line numbers will drift over time and make the doc harder to keep accurate; prefer linking to the file/component name without a specific line number (or use a GitHub permalink if you need an exact reference).
**Reuses:** `SaveToLocalStorageModal` pattern from `ClassicOperation.tsx:544`,
`localStorageSavedTransactions` helper

docs/new-transaction-flow.md:844

  • The document currently ends with # Part 3: Import Transaction but has no content under it. If Part 3 isn’t ready yet, consider removing this header or marking it explicitly as “(WIP)” with at least a short outline, so readers don’t assume content is missing.
# Part 3: Import Transaction


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jeesunikim jeesunikim requested a review from quietbits February 24, 2026 02:39
users can navigate back to any completed step, but cannot skip forward.
Forward navigation always goes through the "Next" footer button

### Shared link handling (MVP)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shared link handling @janewang

New structure — `page.tsx` renders `<BuildFlow />` directly; the `<Tabs />`
component contains nav links, not local state:

> **Tabs component concern:** The existing `src/components/Tabs/index.tsx` uses
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@quietbits what do you think of this approach?

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

1 similar comment
@stellar-jenkins
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog (Not Ready)

Development

Successfully merging this pull request may close these issues.

2 participants