Problem
We have a temporary fix in place for the new Travel feature but it has some limitations:
Solution
- When a user clicks on
Travel tab, redirect the user to New Expensify /travel via the navigateToNewDot function
- If the user was using Expensify Classic, we should not set their
tryNewDot.classicRedirect NVP
- When a user clicks on
Book Travel in New Expensify we should open the browser as we do today, but we should take them back to Expensify Classic in the background.
The intention here is to not take the user back to New Expensify once they return back to the Expensify app.
Issue Owner
Current Issue Owner: @twisterdotcom
Problem
We have a temporary fix in place for the new Travel feature but it has some limitations:
Solution
Traveltab, redirect the user to New Expensify/travelvia thenavigateToNewDotfunctiontryNewDot.classicRedirectNVPBook Travelin New Expensify we should open the browser as we do today, but we should take them back to Expensify Classic in the background.The intention here is to not take the user back to New Expensify once they return back to the Expensify app.
Issue Owner
Current Issue Owner: @twisterdotcom