[codex] harden CLI scheduling payloads#9
Open
pdurlej wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
taskUpdatehelpers for Today, Anytime, Someday, Inbox, and date schedulingsr: 0/tir: 0with explicitnulldate fields--scheduledfrom being cleared wheneditalso assigns an area, project, or headingContext
Several update paths used
Schedule(1, 0, 0)as shorthand for Anytime while assigning projects, areas, or headings. That is risky becausesr=0andtir=0can be interpreted as the Unix epoch rather than "no scheduled date". The create path already uses nullable date fields for this distinction; this patch makes sparse update payloads do the same.Validation
go test ./cmd/things-cli -count=1go test ./...