-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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.
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
[HOLD for payment 2023-12-20] [DISTANCE] LOW: PHASE 1: Wave 5 CLEANUP Refactor navigation among screens related to money request features #26538
Comments
We had some more discussion about this in https://expensify.slack.com/archives/C05DWUDHVK7/p1694542449982949 and I believe we should actually double-down on the URL based navigation. It has lots of benefits with the navigation flow (back buttons, screen animations, etc.). Yes, it is pretty flawed and difficult to understand in its current state. I wouldn't mind taking this issue and having a go at cleaning this up so that it's more predictable and easier to use. |
Two big pieces for this were merged today. I'll keep working on cleanup. Note to self: Try to remove |
I've been slowing chipping away at this over the last two days and have begun to implement a new way of routing and organizing the feature. |
Triggered auto assignment to @anmurali ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
We're good here 😅 Just waiting for this to wrap up and get paid out. |
Still waiting for @anmurali to pay this out. |
1 similar comment
@anmurali Happy New Year! Just a friendly bump for payment 🙇 |
@anmurali Accepted the offer, thanks! |
Paid. |
Remove deep-linking support for screens related to money request
In the current code, deep linking to the screen for each step of money request flow is allowed.
There are logics to handle deep linking to a screen that corresponds to a step in the middle of the money request flow. These logics are not scalable and adds additional complexity.
Let's remove the support for deep linking. All screens should be under a single URL and all steps should be completed under that URL.
Relevant Slack discussion: https://expensify.slack.com/archives/C01GTK53T8Q/p1692998235169129
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: