fix(chat): handle markdown link file paths in chat messages#51
Merged
Conversation
…of browser navigation
…file path detection
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
[App.tsx:1](App.tsx#L1)), clicking them previously navigated the browser to a non-existent URL instead of opening the file in the editor panelacomponent override inMarkdown.tsxto detect file path hrefs and route them throughonFileOpen#L1) before file path detection, since AI models often append line anchors to file pathsTest plan
.texfile to markdown — it will reference output files likebackground.zh.mdas markdown links in its responsehttps://links still open in a new tab as beforeApp.tsxin backticks) still work as before