Skip to content
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

[7.0] Fix engine results order #369

Merged
merged 3 commits into from
Apr 1, 2019
Merged

[7.0] Fix engine results order #369

merged 3 commits into from
Apr 1, 2019

Conversation

driesvints
Copy link
Member

@driesvints driesvints commented Apr 1, 2019

This commit fixes the sorting of Algolia results. Instead of letting this get reset by the collection we should use the sorting results from Algolia itself since it already correctly sorts the search results.

The first two commits of this PR are adjustments to the test suite I did to cleanup unnecessary fixtures. In essence, this PR is only the last commit: dafbfa7

Fixes #341

For some reason there were way more fixtures then there were suppose to be. This commit refactors the fixtures so they're included in the only classes they're used and reduces them to only the minimum amount needed.
This commit fixes the sorting of Algolia results. Instead of letting this get reset by the collection we should use the sorting results from Algolia itself since it already correctly sorts the search results.
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.

AlgoliaEngine::map does not respect the order of the Engine results
2 participants