feat: resolve markdown links for fetched pages#144
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Resolve relative anchor and image URLs in fetched HTML markdown against the final response URL. Preserve simple code fence language hints from
<pre class="language-...">/<pre class="lang-...">.Why
AI agents consume markdown outside the original page context. Absolute links keep citations and follow-up fetches usable after conversion. Language-tagged code fences also improve downstream code understanding.
How
Added
html_to_markdown_with_base_url, wired the default fetcher to call it with the final URL, and kepthtml_to_markdownbackward-compatible for direct conversion. Added converter and fetcher tests.Risk
Checklist