You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I've been tinkering in my app using meilisearch-php v1.12 and when getting an ApiException I get a errorLink but the error code does not exist in the doc, is the Exception outdated here ? Should I post the issue in the docs repo ?
Here is the
Screenshots or Logs
If applicable, add screenshots or logs to help explain your problem.
{#2262 // vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:145
#message: ?
#code: 400
#file: "
/var/httpdocs/manager/vendor
/meilisearch/meilisearch-php/
src/Http/Client.php
"
#line: 186
+httpStatus: 400
+message: """
Attribute `id` is not filterable. This index does not have configured filterable attributes.
1:3 id NOT IN [1, 2, 3]
"""
+errorCode: "invalid_filter"
+errorType: "invalid_request"
+errorLink: "https://docs.meilisearch.com/errors#invalid_filter"
+httpBody: array:4 [
"message" => """
Attribute `id` is not filterable. This index does not have configured filterable attributes.
1:3 id NOT IN [1, 2, 3]
"""
"code" => "invalid_filter"
"type" => "invalid_request"
"link" => "https://docs.meilisearch.com/errors#invalid_filter"
],
...
}
This is annoying as I don't really know what's going on
Environment (please complete the following information):
OS: MacOS 14.4.1
Meilisearch version: 1.12
meilisearch-php version: 1.12
The text was updated successfully, but these errors were encountered:
Description
I've been tinkering in my app using meilisearch-php v1.12 and when getting an
ApiException
I get aerrorLink
but the error code does not exist in the doc, is the Exception outdated here ? Should I post the issue in the docs repo ?Here is the
Screenshots or Logs
If applicable, add screenshots or logs to help explain your problem.
This is annoying as I don't really know what's going on
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: