Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Pipeline Plan 242

Seth Ford edited this page Mar 10, 2026 · 5 revisions

The implementation is already complete and all tests pass. Here's the summary:

Implementation Plan (Already Complete)

The fix has been implemented across 7 commits on this branch. The core changes are:

What was changed

scripts/sw-loop.sh (18 lines changed):

  • Case 2 (line 579): Extended condition from first_char == "[" to first_char == "[" || first_char == "{" so JSON objects enter the jq parsing path
  • Added branching logic within Case 2 to handle arrays (.[-1].result) vs objects (.result) and arrays (.[].content) vs objects (.content)
  • Case 3 (line 609): Now only reachable when jq is genuinely unavailable, making the "jq not available" warning accurate

scripts/sw-loop-test.sh (45 lines added):

  • Test 23: 4 assertions covering JSON object extraction:
    1. Extracts .result from JSON object
    2. Falls back to .content from JSON object
    3. Shows placeholder for JSON object with neither field
    4. Verifies the misleading "jq not available" warning does NOT appear when jq IS available

Current status

  • All 69 loop tests pass
  • The branch has the fix + autonomous cleanup iterations
  • Ready for PR creation

Definition of Done

  • JSON objects ({...}) are parsed by jq instead of falling through to misleading warning
  • JSON arrays ([...]) continue to work as before
  • The "jq not available" warning only appears when jq is genuinely unavailable
  • .result extraction works for both formats
  • .content fallback works for both formats
  • Tests cover all edge cases
  • All existing tests still pass

Clone this wiki locally

AltStyle によって変換されたページ (->オリジナル) /