Extraction chains #437
Closed
Extraction chains #437
Conversation
This file contains 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
|
@MrTpat i will create v4 for this, ok? |
|
@MrTpat please do on PR on V4 https://github.com/feder-cr/Auto_Jobs_Applier_AIHawk/tree/v4 |
|
@MrTpat any updates? |
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.
So this introduces a concept of "extraction chains" for our job parsing. Certain issues: (#114) are happening because there are parsing changes necessary when LinkedIn changes something on their end. Instead of changing our parsing code each time, we can add a new parser here when we encounter some new linkedin HTML format.
Shoutout to @pafthinder for his initial correct implementation which I've included here. This fixes THAT issue and fixes issues I had been having myself.