fix(javascript): encode query parameters #973
Merged
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.
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-629
Changes included:
Reported by the Predict team
The query parameters were serialized but not encoded, I'm not sure when it has been removed since this piece of code comes from the current implementation.
It seems that on the Search API side, it either does not require the parameters to be encoded, or silently fails. Either way, it should now behave like in the current JavaScript client.
echoRequester: use same encoding/decoding than client
🧪 Test
search requests work:
yarn docker playground javascript search
predict requests work:
.env
yarn docker playground javascript predict