A failed trip calculation no longer leaves the last place's weather on screen
When you are building a plan and the app cannot work out the route — no signal, or no usable starting point — it clears the travel numbers it can no longer stand behind. It was not clearing the weather beside them, so you could be looking at a fresh route to a new destination sitting next to the forecast for the previous one, both looking equally current. Plans save whatever is on screen, so that mismatch could outlive the failure that caused it. The endings that can prove their forecast is out of date now clear it. The interesting part is what stopped this being a much bigger change. The work was specified as "apply the rule the trip editor already uses", and reading that rule showed it said close to the opposite: it deliberately keeps existing numbers when a failure has not changed the shape of the trip, because they are still true. Copying it as described would have thrown away good data on a passing network blip. Two of the three cases turned out to need something the creation screen does not record yet — which place a forecast belongs to — so they are tracked separately rather than guessed at.
Share This Ship
🔧 Shipped: A failed trip calculation no longer leaves the last place's weather on screen 🧵
When you are building a plan and the app cannot work out the route — no signal, or no usable starting point — it clears the travel numbers it can no longer stand behind.
It was not clearing the weather beside them, so you could be looking at a fresh route to a new destination sitting next to the forecast for the previous one, both looking equally current.
Plans save whatever is on screen, so that mismatch could outlive the failure that caused it. The endings that can prove their forecast is out of date now clear it. The interesting part is what stopped this being a much bigger change.
The work was specified as "apply the rule the trip editor already uses", and reading that rule showed it said close to the opposite: it deliberately keeps existing numbers when a failure has not changed the shape of the trip, because they are still true.
Copying it as described would have thrown away good data on a passing network blip. Two of the three cases turned out to need something the creation screen does not record yet — which place a forecast belongs to — so they are tracked separately rather than guessed at.
Follow the build → build-log-five.vercel.app #ios #reliability #usability #buildinpublic