fix: ensure iterate command respects --json flag for all output #195
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
ereslibre
approved these changes
Sep 22, 2025
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.
Fix the iterate command to properly handle the
--jsonflag by ensuring all console output is suppressed when JSON mode is active. This resolves VSCode extension errors when running iterate commands.Changes
fafrom zod/locales--followoption which was not being usedstartDockerExecutioncall to pass the json option correctlyNotes
The issue was that the iterate command was outputting extra logs when the
--jsonflag was passed, causing the VSCode extension to fail when parsing the JSON response. This fix ensures that the json option is properly passed through to all relevant functions.Closes #176