fix(staged): parse notes after inline metadata fences#790
Conversation
Signed-off-by: Matt Toohey <contact@matttoohey.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e25d04f493
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| while search_from < text.len() { | ||
| let Some(rel_pos) = find_suggested_next_steps_opening_fence(&text[search_from..], marker) |
There was a problem hiding this comment.
For notes whose body itself includes a fenced suggested-next-steps example after the --- separator, this whole-message stripping loop deletes that body content before extract_note_content returns it, so the stored note is silently corrupted. Limit the removal to the assistant metadata before the selected note separator, or locate the separator first and preserve the original body.
Useful? React with 👍 / 👎.
1 participant
Summary: