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
Database Driver & Version: PostgreSQL 17 (Also tested with MySQL 8.0.33)
Expected Behaviour:
In the Filament panel, when creating a Product Association with a previously selected product, in the product drop-down list you should do a search, regardless of case and find existing products.
Actual Behaviour:
when I try to create a Product Association, when searching for a product to relate to this one, in the Select component called 'product', it is not able to find anything, it makes no difference to me if I search with all lowercase or by writing the name of a product exactly the same, no product is found.
I actually tested this without using Laravel Scout.
Steps to reproduce:
In the config/lunar/panel.php file, set the 'scout_enabled' parameter to false.
Create 2 products.
In one of them, edit and try to create a Product Association by searching in the Select component's search box by typing the name of your other product.
The text was updated successfully, but these errors were encountered:
Expected Behaviour:
In the Filament panel, when creating a
Product Association
with a previously selected product, in the product drop-down list you should do a search, regardless of case and find existing products.Actual Behaviour:
when I try to create a
Product Association
, when searching for a product to relate to this one, in the Select component called 'product', it is not able to find anything, it makes no difference to me if I search with all lowercase or by writing the name of a product exactly the same, no product is found.I actually tested this without using Laravel Scout.
Steps to reproduce:
config/lunar/panel.php
file, set the 'scout_enabled' parameter to false.Product Association
by searching in the Select component's search box by typing the name of your other product.The text was updated successfully, but these errors were encountered: