chore(refactor): move scraper type to a constant #2
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
Signed-off-by: mudler <mudler@localai.io>
teslashibe
pushed a commit
that referenced
this pull request
Jul 14, 2025
chore(refactor): move scraper type to a constant
grantdfoster
pushed a commit
that referenced
this pull request
Oct 13, 2025
…#2) - Rename LinkedInSearchArguments to LinkedInArguments for broader scope - Add PublicIdentifier field to support individual profile fetching - Maintain backward compatibility with deprecated type alias - Field uses omitempty tag to preserve existing search functionality - Enables dual-purpose struct for both search and profile operations
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.
To make it more consistent and helping out by giving hints where things are constructed when creating new scrapers