Conversation
- Fix splitLines logic to split by newlines before normalizing whitespace in linkedinSearch.ts and linkedinEvents.ts - Add e2e assertions to ensure title and date_time fields are reasonably sized
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
1 participant
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
Fixes #596 by preventing over-extraction of
titleanddate_timein events search.Changes
linkedinEvents.tsandlinkedinSearch.ts, the code previously callednormalize((card as HTMLElement).innerText)before splitting by newlines. Sincenormalizereplaces all whitespace (including newlines) with spaces, the split yielded an array of length 1, mapping the entire card text tolines[0].events.e2e.test.tsandsearch.e2e.test.tsto ensuretitleanddate_timeare not massively long strings.Closes #596