Frappe Search Integration #215
Closed
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
We are using website search only as a fallback for when redisearch fails to work. It's better to remove both and maintain just one type of search for now. |
Passing run #291 ↗︎
Details:
Review all test suite changes for PR #215 ↗︎ |
|||||||||||||||
|
Closing this PR as we move to a Python based implementation of Frappe Search. Also, we will first implement in Gameplan to get internal feedback before deploying to Wiki. |
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 integrates Frappe Search into Wiki.
The previous implementation also used website search. Is this necessary? If so, how will we implement it here?
(Will revert the formatting soon).