Repository navigation
fix: preserve plain feed text and filter before presentation - #54
Merged
Merged
Conversation
This was referenced Oct 21, 2026
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.
Plain JSON Feed and Atom content such as Vec was interpreted as HTML and lost text. Honor the source MIME type, preserve literal text, and escape Markdown/HTML output, including entity-like strings.
Run keyword matching against full normalized plain source text before rendering, truncation, or omission, so changing content_format or max_content_chars no longer changes which items match. Stable item-id construction stays unchanged; corrected rendering can change content_hash.
Validation: formatting, clippy with warnings denied, the full test suite (294 tests), and release build. Parser regressions cover bodies and summary fallbacks, text/HTML/Markdown, literal tags/entities, and query selection across formats and caps.
Stack position: 2 of 4; targets the cache/input branch. Merge the stack in order. Consolidated documentation is in the final PR.
Merge order: #53 → #54 → #55 → #56.