fix(search): expose pretty JSON option - #183
Open
ayushcodes13 wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
ayushcodes13
force-pushed
the
fix/181-search-pretty-option
branch
from
421b2e7 to
4d18d6f
Compare
August 10, 2026 18:01
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
Closes #181
Test Plan
The new CLI argv test failed before the option registration was restored because search help did not include --pretty; it passes after the change.
Summary by cubic
Fixes #181 by restoring the -p, --pretty flag for firecrawl search to enable pretty-printed JSON and show it in --help. Preserves behavior where --pretty implies JSON and adds a CLI argv test to prevent regressions.
Written for commit 4d18d6f. Summary will update on new commits.