-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix: filter out markdown delimiters from next edit responses #8056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 2 files
|
🎉 This PR is included in version 1.24.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Filters out backticks from the start and end of next edit completions, which was happening sometimes in markdown files.
Summary by cubic
Remove markdown code fences from next edit completions so we don’t insert stray ``` lines in markdown files. This makes generated edits cleaner and avoids malformed code blocks.
and a trailing line that is exactlyin postprocessCompletion, without touching inline backticks.