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
Description of what the bug is about.
Using the provided example we get a react warning:
Each child in a list should have a unique "key" prop.
Check the render method of `Hits`. See https://reactjs.org/link/warning-keys for more information.
Expected behavior
What you expected to happen.
The example should provide a unique key to each hit, so that the warning is not triggered.
Current behavior
What happened.
The code sandbox hit component has a key property, but it does not remove the warning:
A user said it appeared when he moved from Algolia to Meilisearch, see Discord. As I told the user, I guess Algolia uses by default the objectID they generate for each document, but since we don't use an objectID we should probably provide an example that does not trigger a warning.
Description
Description of what the bug is about.
Using the provided example we get a react warning:
Expected behavior
What you expected to happen.
The example should provide a unique key to each hit, so that the warning is not triggered.
Current behavior
What happened.
The code sandbox hit component has a key property, but it does not remove the warning:
Screenshots or Logs
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: