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
Currently, routes in in <NewWalletViewsSwitch /> (or at least, that's where they're handled at the time of writing) are manually re-handled, because of styling issues, mostly:
After we go live and delete previous wallet flow code, we'll be able to apply the style we want in each component, hence ensuring we don't produce any regression, and making it so that we don't have to reinvent the wheel and don't need to have another place with full-fledged routes handling logic.
References and additional details
N/A
Acceptance Criteria
Routes are handled in a single-place again after go-live
Dead code from previous components is removed
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered:
Overview
Once we go live with new wallet flow, routes handling will need to be re-consolidated by leveraging
web/src/context/WalletProvider/config.ts
Lines 368 to 386 in c708b53
Currently, routes in in
<NewWalletViewsSwitch />
(or at least, that's where they're handled at the time of writing) are manually re-handled, because of styling issues, mostly:web/src/context/WalletProvider/NewWalletViews/NewWalletViewsSwitch.tsx
Lines 56 to 88 in c708b53
After we go live and delete previous wallet flow code, we'll be able to apply the style we want in each component, hence ensuring we don't produce any regression, and making it so that we don't have to reinvent the wheel and don't need to have another place with full-fledged routes handling logic.
References and additional details
N/A
Acceptance Criteria
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: