-
Notifications
You must be signed in to change notification settings - Fork 216
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
Expose rule.consequence.promote.objectIDs string array #1155
Labels
Comments
looks like we only accept |
Haroenv
added a commit
that referenced
this issue
May 20, 2020
doesn't have a test yet, but allows you to base on top of this. fixes #1155
nunomaduro
pushed a commit
that referenced
this issue
Jun 9, 2020
doesn't have a test yet, but allows you to base on top of this. fixes #1155
nunomaduro
pushed a commit
that referenced
this issue
Jun 9, 2020
doesn't have a test yet, but allows you to base on top of this. fixes #1155
This feature can't be merged yet: algolia/algoliasearch-client-specs-internal#118. |
Haroenv
added a commit
that referenced
this issue
Aug 6, 2020
* feat(rule): add group promotes doesn't have a test yet, but allows you to base on top of this. fixes #1155 * prettier * chore(group-promotes): fixes object ids readonly type Co-authored-by: Nuno Maduro <enunomaduro@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On top of the existing
objectID
(singular) string field, a newobjectIDs
(plural) string array field is now be exposed in the
rule.consequence.promote
Rule object representation. This lets the user easily promote a full group of
objects without letting some priority conflicts to shift some objects at the end
of the promoted object list.
The text was updated successfully, but these errors were encountered: