feat: add Perplexity support - #17
Open
chanyut12 wants to merge 1 commit into
Open
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
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.
Summary
This PR adds Perplexity support to Scroll.
It introduces a new
perplexityprovider and wires it into the existing extension flow while keepingthe current architecture and behavior for the existing providers intact.
What Changed
Implementation Notes
This change was kept intentionally minimal.
showSidebarand the existing provider flow were kept aligned with the current codebaseThe Perplexity parser now:
Validation
Ran locally:
npm run typechecknpm run buildnpm run build:firefoxManual testing completed:
Risks / Limitations
Perplexity parsing depends on the current DOM structure. If Perplexity changes its layout, the
provider may need follow-up selector updates.