Closed wbazant closed 3 months ago
This PR is ready to go as is, but I started doing more work on top of it, as a warm-up for 3. above.
The goal was #407 - in "new position" state, going to settings and back should bring back the marker, which was the most trivial feature that uses saved location data I could think of. Then I found the tabs code, and made the change that closes #411 .
Now also closes #407
Now also closes #412
@wbazant This feels like a major step forward! Do you want to merge now or keep building on this branch (e.g. for #359)?
After trying out the suggested fix to #412, I agree with my https://github.com/falling-fruit/falling-fruit-web/issues/412#issuecomment-2205871068: I think the marker should appear immediately, but the location should only display once the latest pending is fulfilled.
@ezwelty I have these commits on top: https://github.com/wbazant/falling-fruit-web/pull/1 .
I tried to keep the branch to be good to merge at any point, so we could merge it now and I'll open a new draft PR for editing the location with the intermediate state in Redux?
@wbazant Would it be convenient for you to adjust the #412 behavior in this branch before we merge? If not, and you would rather tackle that in a later PR, I could merge now. But I'm in no hurry to merge; whatever is easiest for you.
Sure, I've made the relevant lines like on the other branch.
The reducers are just in their simplest state - and will probably grow if we put more stuff there, like intermediate states of form or drawer state - and there aren't really any huge benefits from the PR by itself but it should help later. From the original points:
I checked we still do a redirect from a bare URL to the one with coordinates
Opened new issue, #409