A FarmBot patch stops planted dates shifting by a day
A Claude Code-assisted patch parses planted dates in the FarmBot device's time offset, rather than the browser's. The contributor reports regression tests across five host timezones.
Credits
- Patch author David-VanAssche Source ↗
Earliest dated source: Details reviewed:
The full story
FarmBot's planted-date editor and bulk updater could save a selected date one day earlier or later when the browser and device used different time offsets. The parser created midnight in the browser's timezone before changing its displayed offset, leaving the stored instant on the wrong device day.
The contributor used Claude Code to change parsing to midnight at the device's offset. They report new cases for five UTC offsets, exercised under five host timezones: all ten new cases failed before the change and passed after it. Type checking and lint passed; the full suite still had one reported unrelated intermittent failure. The pull request is open, so this is a proposed application fix rather than a released FarmBot update.
Before and after
- Starting problem
- A planted date could shift to the previous or next device day when browser and device offsets differed.
- Reported result
- The contributor reports ten new exact-timestamp cases passing after parsing at the device's UTC offset.
Device and compatibility
- FarmBot Web App
Planted-date editor and bulk-update components; proposed patch tested in software, not a hardware movement change.
Source ↗
What Claude did
- Date-parsing fix and regression tests, explicitly credited as generated with Claude Code.Claude Code Source ↗
How it was done
Tools
Themes
Loading themes…
Sources
From the maker's own write-up or code. We summarise what they report; we haven't tested it ourselves.
- GitHub: Fix planted date saving one day off (#2388)
The proposed timezone fix, explicit Claude Code credit and contributor's test report.