Skip to content

feat(findAnswers): implement the new method #1219

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

Merged
merged 10 commits into from
Nov 16, 2020
Merged

feat(findAnswers): implement the new method #1219

merged 10 commits into from
Nov 16, 2020

Conversation

Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Nov 3, 2020

  • adds findAnswers to node / browser (not lite for now)
  • fix small typo in SearchOptions
  • add an integration test

- adds searchForAnswers to node / browser (not lite for now)
- fix small typo in SearchOptions
- add an integration test
@Haroenv Haroenv requested review from yannickcr and PLNech November 3, 2020 15:34
@PLNech PLNech changed the title feat(searchForAnswers): implement the new method feat(findAnswers): implement the new method Nov 6, 2020
@chloelbn chloelbn self-requested a review November 9, 2020 11:04
@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 663adbf:

Sandbox Source
javascript-client-app Configuration

const client = algoliasearch(credentials.appId, credentials.apiKey);

// TODO: remove this customization once the engine accepts url encoded query params
client.transporter.userAgent.value = "answers-test";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Haroenv to be clear, are we waiting for the engine fix, so that we can get rid of this line before merging this PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @eunjae-lee, the engine fix won't be happening soon, so I'd rather merge this and prepare a v1.1 PR for when the engine has catched up :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it. thanks for clarification!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants