move all search endpoints to fastapi #11634
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
…he legacy implementation.
…rch JSON implementation.
…to search endpoints.
… and a mock for its fulltext search dependency.
…ebpy `search/inside` endpoints, including a new mock for the synchronous search function.
…duce Solr query mocks.
…ontract test for it.
…tion and contract tests for consistent behavior with web.py.
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.
This PR moves all the search endpoints to fastapi.
Note: most of the test code here will be deleted quickly once this stuff is running on production. It's AI generated but gives me a bit more confidence that there aren't any major discrepancies in how we call things. The small ones are noted in the tests. Mostly differences around when to pass none due to the unified Pagination model.
Technical
Testing
Screenshot
Stakeholders