Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

Distinct should default to false only when the user tries to set it #107

Closed
bobylito opened this issue Jun 15, 2015 · 3 comments
Closed
Assignees
Milestone

Comments

@bobylito
Copy link
Contributor

The value for distinct should only be set in the case the user sets it because he might have set it in its dashboard. @pixelastic reported this one.

@bobylito
Copy link
Contributor Author

@redox what do you think?

@bobylito
Copy link
Contributor Author

I created a branch for that : fix/107

@bobylito bobylito self-assigned this Jun 16, 2015
bobylito added a commit that referenced this issue Jun 17, 2015
Fix #107 : fix rules for distinct
@bobylito bobylito added this to the 2.1.1 milestone Jun 17, 2015
@bobylito
Copy link
Contributor Author

Associated PR : #109

vvo pushed a commit that referenced this issue Jun 19, 2015
  * FIX : #107 Apply rules to distinct to prevent the API to return an error
  * FIX : make algoliasearch-helper requireable + browserifyable by
    removing the global envify transform
dhayab pushed a commit to algolia/instantsearch that referenced this issue Jul 10, 2023
dhayab pushed a commit to algolia/instantsearch that referenced this issue Jul 10, 2023
  * FIX : algolia/algoliasearch-helper-js#107 Apply rules to distinct to prevent the API to return an error
  * FIX : make algoliasearch-helper requireable + browserifyable by
    removing the global envify transform
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant