Changes due to the implicit index creation #124
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.
Related to meilisearch/integration-guides#48
Changes:
$client->index($uid)
: replaces$client->getIndex($uid)
. Does not do any HTTP call but only returns anIndex
instance.Index
class:primaryKey
$index->fetchRawInfo()
: returns an array of index$index->fetchInfo()
: returns anIndex
instanceBreaking changes:
$client->getIndex($uid)
now does an HTTP call. Use$client->index($uid)
instead.$client->updateIndex
returns anIndex
instance.$index->getPrimaryKey()
does not do any HTTP call, but only return theprimaryKey
attribute. Use$index->fetchPrimaryKey()
if you want the same behavior as the old$index->getPrimaryKey()
$index->show()
is removed and replaced by$index->fetchInfo()
(returns an instance) and$index->fetchRawInfo()
(returns an array)$client->showIndex($uid)
is removed. Use$client->getIndex($uid)
(returns an instance) or$client->index($uid)->fetchRawInfo()
(returns an array) instead.