Include resume entry prose in exported search text - #155
Merged
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
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.
The exported
resumeSearchTexthelper drops non-bullet paragraphs beneath an entry subtitle. For example,Processed bathymetry observations.remains inparseResume(...).sections[0].entries[0].markdownbut the exported search text contains nobathymetry.Use the full entry Markdown as the body when flattening each entry, retaining its title and place. This preserves later paragraphs and list content without repeating subtitle/highlight text. The fix is limited to the exported helper; the current repository candidate-directory implementation does not call it, so this does not claim to change the live directory search.
Validation: four independent behavioral checks pass (ordinary paragraphs, non-Latin text across entries, full body without duplicated structured lines, and existing-field preservation). The unchanged baseline fails three and passes one. Both focused
search texttests pass.npm run buildandtsc -p tsconfig.json --noEmitpass.Submitted under the published $0.25 USD-equivalent reward per valid bug-fix PR, using the existing application and settlement conversation. Settlement remains native SOL on Solana mainnet, subject to payer acceptance and confirmation of the exact token amount. No reward is claimed as received.