linkedin: bugfix-data-extraction #2

Merged
nilsnh merged 5 commits from bugfix-data-extraction into main 2026-01-17 15:02:52 +01:00
Owner

I realized that I had thought all wrong about how to extract user data from the page.

This PR changes the data extraction strategy to fetch data from the DOM and not the various code blocks on the page. Using the previous approach I was only able to extract my own user data. For my contacts' data I had to rely on navigating the DOM itself.

It works on desktop and mobile for now, but we never know how fast LinkedIn's frontend will be changing.

I realized that I had thought all wrong about how to extract user data from the page. This PR changes the data extraction strategy to fetch data from the DOM and not the various code blocks on the page. Using the previous approach I was only able to extract my own user data. For my contacts' data I had to rely on navigating the DOM itself. It works on desktop and mobile for now, but we never know how fast LinkedIn's frontend will be changing.
I had misjudged the purpose of the data in the code blocks
on the page, they're just for data about the logged in user.
Therefore I had to pick data points from the actual loaded
html.

Reworked tests to start using JSDOM.
nilsnh merged commit 324c35ef6b into main 2026-01-17 15:02:52 +01:00
nilsnh deleted branch bugfix-data-extraction 2026-01-17 15:02:53 +01:00
nilsnh referenced this pull request from a commit 2026-01-17 15:02:53 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nilsnh/rolodex!2
No description provided.