Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Routing: ConfirmView should not use route params #575

Open
Danziger opened this issue Dec 10, 2024 · 0 comments
Open

Routing: ConfirmView should not use route params #575

Danziger opened this issue Dec 10, 2024 · 0 comments
Labels
good first issue Good for newcomers ready for dev

Comments

@Danziger
Copy link
Contributor

Danziger commented Dec 10, 2024 •
edited
Loading

ConfirmView uses route params and TempTransactionStorage, and there are some duplicate values between the two. It would be ideal to stop using route params altogether and only use TempTransactionStorage to load all the required data (including quantity and token (process) ID).
@Danziger Danziger changed the title Routing: ConfirmView and RecipientView route params Routing: ConfirmView should not use route params Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers ready for dev
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Danziger