support search recency filter for perplexity #1025
Merged
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
narengogi
changed the title
VisargD
approved these changes
Apr 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Author Description
(optional)
Title: Support Search Recency Filter for Perplexity
🔄 What Changed
response_formatparameter in Perplexity AI chat completionsearch_recency_filterparameter in Perplexity AI chat completion🔍 Impact of the Change
This enhancement allows users to filter search results by recency and specify response format when using Perplexity AI's chat completion functionality, providing more control over the search results and response formatting.
📁 Total Files Changed
1 file modified with 8 additions and 0 deletions.
🧪 Test Added
N/A - No tests were added in this PR.
🔒 Security Vulnerabilities
N/A - No security vulnerabilities were identified in this change.
Related Issues: N/A
Quality Recommendations
Consider adding unit tests to verify the new parameters work as expected
Add documentation or comments explaining the valid values for the new parameters