Closed DerekCaelin closed 1 week ago
I can repro this on v148.
@knipec I just reviewed this and think we should, instead, remove the Create Site Here button from the soil info sheet.
@CourtneyLee333 Sweet, happy to just remove it :) That's the only place you know of that something navigates to another thing in an overlay sheet, right?
For future engineer reference, this is because overlay sheets are not part of the navigation stack. I think it makes sense to as much as possible treat them as a dead end in navigation flow. However, if we do need to allow that in the future, some approaches Ruxandra and I discussed:
Currently we have a stack of overlay sheets in this path: Top Soil Matches > open a soil info overlay sheet > tap on InfoButton for Location Score or Soil Properties Score > opens info overlay sheet
It seems to switch one overlay sheet for the other, but the Location Score and Soil Properties Score sheets are currently implemented incorrectly and need to be rebuilt with the proper component. If we need to make overlay sheets a dead end in this case, I think making the soil info sheet a screen instead would probably be best.
Ok, I think that's fine!
This is confusing because there are two different libraries at play for concepts that to the user probably both seem like they're about navigation: the react-navigation
library, and the gorhom
library for bottom sheets / overlay sheets.
In the case you mention it's actually just opening another gorhom
sheet, not using the react-navigation
library (via our useNavigation
hook) to navigate sheets. So there still wouldn't be react-navigation
stuff coming from the overlay sheet.
Confirmed this is fixed in 159.
App Version
142
Account
No response
Platforms
Description
The Soil Info sheet isn't closing when the user selects "create site" and the user doesn't see the form until they manually close the sheet
Steps to Reproduce
Expected behavior
sheet closes and the user sees the "create site" form
Actual behavior
sheet remains open, user needs to manually close it to see the form
Additional context
No response