prime servings jq examples reference 'Day' field; actual JSON field is 'RecordedTime' #25

Activity

1. github-actions

   assigned

   DTTerastar

   on Apr 26, 2026
2. DTTerastar commented on Apr 26, 2026

   

   DTTerastar

   on Apr 26, 2026

   CollaboratorAuthor

   More actions

   @claude Please fix
3. claude commented on Apr 26, 2026

   

   claudebot

   on Apr 26, 2026 – with Claude

   Last edited by claude

   More actions

   Claude finished @DTTerastar's task in 10m 12s —— View job • claude/issue-25-20260426-0039 • Create PR ➔

   ---

   Fixing jq examples: Day → RecordedTime

   • Read CLAUDE.md for repo-specific instructions
   • Locate jq example strings referencing Day field
   • Add date-based servings jq example using .RecordedTime
   • Add GOTCHA about Day being null in servings JSON
   • Commit and push the fix

   Changes made to cmd/prime.go:

   1. New jq recipe — added a concrete date-filtering example for servings using .RecordedTime:

      # All servings on a specific day
      crono-export servings --since 7d --format json | jq '[.[] | select(.RecordedTime | startswith("2026-04-25"))]'
      

   2. New GOTCHA — warns that the Day field in servings JSON is always null and directs users to RecordedTime:

      - 'servings' JSON rows contain a 'Day' field that is always null — use
        'RecordedTime' (an ISO-8601 timestamp) for any date-based filtering.
      
4. DTTerastar

   closed this as completedin #26on Apr 26, 2026
5. DTTerastar

   added a commit that references this issue on Apr 26, 2026

   docs(prime): add RecordedTime date example and warn that Day is null …

   ...

   This issue will close once commit dfe32bc is merged into the 'main' branch.

   dfe32bc