feat: temporarily re-introduce v4/search/autocomplete #748
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
Signed-off-by: Akiff Manji <akiff.manji@quartech.com>
esune
approved these changes
Jun 7, 2023
|
@WadeBarnes leaving teh promotion of this new version to test/prod to you |
|
LGTM. The OrgBook Search UI is not returning anomalous results. |
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 is a temporary re-introduction of
v4/search/autocompleteto give time for end users to migrate off. The endpoint is marked asDEPRECATEDand should be removed as soon as possible.The
v3endpoint is not impacted (to confirm, it has been tested against OrgBook BC). All changes in this PR are isolated to thev4endpoint (with some minor technical debt introduced).