Add index name to error message about meilisearch

[cisco877]

I would like to see if I can work on this issue, would that be ok?

[curquiza]

Hello @tacman
Thank you for this report.

This would be a nice improvements

Any contribution is welcome ❤️

⚠️ More info for the contributor:

This issue is not hard, but not trivial. Knowledge in Rust are required.
It will probably mean a lot of small mechanical changes to multiple files.

We would probably want the added context for most if not all milli::UserError . The thing is that in this location of the engine, we don't have the information of the index name.
So it would have to be injected at the point where the error is caught in the webserver part of the engine, which will be many different points depending on where we're calling milli functions that can error

[tacman]

Perhaps the change could be make in the meilisearch php library?

[curquiza]

We would rather handle this at the source (engine) than changing things in 10 library

[tacman]

Makes sense. In addition to the index, I guess it'd be helpful to have all the details. Sometimes I run meilisearch in docker, and in different projects it listens on different ports, and sometimes calls a remote server. So in addition to the index, I'd want to know the server and port.

[curquiza]

We would rather not prioritize the port addition to solve this issue -> let's focus on the index name as a first step. From a product perspective, it does not seem relevant to us to have this information in the error, so we need more product discussion before validating it. We are a small team so we are careful about everything we add because can be tedious to update and maintain

Btw, as a workaround, in the meantime you can have all the information in the URL you try to reach: index name and port

[curquiza]

Hello @cisco877

Thanks for your interest in this project 🔥 You are definitely more than welcome to open a PR for this!

For your information, we prefer not assigning people to our issues because sometimes people ask to be assigned and never come back, which discourages the volunteer contributors from opening a PR to fix this issue.
We will accept and merge the first PR that fixes correctly and well implements the issue following our contributing guidelines.

We are looking forward to reviewing your PR 😊