-
Notifications
You must be signed in to change notification settings - Fork 21
feat(javascript): allow legacy signature for search
method
#665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for api-clients-automation canceled.
|
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
2f7f48d
to
d827f95
Compare
d827f95
to
ca56545
Compare
ca56545
to
0d0450c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hate it great job !
Ahaha sacrifices! |
templates/javascript/api/operation/legacySearchCompatible/implementation.mustache
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great !
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-528
Changes included:
As discussed during our tech syncs with the fx team, we've decided to support the legacy signature for the
search
method and handle the logic on our side.In this PR, we implement the logic in the
client-search
,algoliasearch
andalgoliasearch-lite
packages.As
algoliasearch
inherits of methods from theclient-search
package, andalgoliasearch-lite
is a lighter copy of it, I've added tests in this client to ensure the alias works smoothly.🧪 Test
yarn workspace @experimental-api-clients-automation/algoliasearch test
yarn workspace javascript-playground start:algoliasearch