Linkedin scrapper fixes#84
Open
HalaHamdi wants to merge 32 commits into
Open
Conversation
…i/cmp-docs into linkedin-scrapper-fixes
…i/cmp-docs into linkedin-scrapper-fixes
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for cmp-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Owner
|
Owner
|
|
…i/cmp-docs into linkedin-scrapper-fixes
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
3 participants
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.
Made progress in #81
🚀 What this PR does
Fix LinkedIn‑scraper “current_position” bugs
Corrects logic that was mis‑parsing the
current_positionfield on some profiles.Add dynamic GitHub Action for Classes YAMLs
Loops over all
C20xx.yamlandC20xx_Credit.yamlfiles inpublic/department/Extras/Classes/, runs the scraper on each file sequentially, commits any changes, and pushes back to the branch. Scheduled to run automatically on the 1st of every month and also triggerable via “Run workflow.”Secret‑only setup
Requires a repo secret
LINKEDIN_COOKIES_JSONcontaining your exported cookies JSON (via “Export cookie JSON file for Puppeteer” mentioned in ⭐️ Create a Github Action for Automatic LinkedIn Scraping #81). Ensure your LinkedIn session is active when you generate that file to prevent expiration.⚙️ Remaining work
Batch LinkedIn API requests
Currently implemented but not yet wired into the main flow.
Error‑handling for corner cases
Some profiles still throw unhandled exceptions.
Code cleanup & refactoring
Performance optimizations and better module structure.