feat(reader): preprocess fetched data with Jina Reader API #252
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.
Closes #250
Applied changes based on Issue #250.
I’ve wired up the
--fetch
handler to use the Jina Reader proxy (prefixing each URL withhttps://r.jina.ai/
) so that all fetched content is preprocessed through Jina. I also updated both the “Issues” and “PRs” examples in the README to document this behavior.Summary of changes:
--fetch
block, replaced directaxios.get(url)
with/codex --fetch …
snippet (in both the Issues and PRs sections), added a note:“By default, URLs are fetched and preprocessed via the Jina Reader API by prefixing each URL with
https://r.jina.ai/
, which retrieves the processed content.”Let me know if you’d like any further tweaks or tests around this!