[Autocomplete] Tom Select 2.6.1 Entity Search broken

[Chris53897]

After Upgrading Tom Select 2.6.0 to 2.6.1 the Entity Search does not work properly.

2.6.0 correct

2.6.1 no filtering

i am not sure where the problem is, and if this repo is correct

[Chris53897]

orchidjs/tom-select#998 (comment)
@mmarton I just notice your comment

[mmarton]

I didn't had the time for a reproducer, if you has one, feel free to add
orchidjs/tom-select#1039

[ehymel]

Before I found this bug report, I used Junie in PHPStorm to try and find a solution. After some work the AI offered the following workaround. I don't know if the reason is correct (see comments in code), but I can confirm that this works for me.

The suggested "fix" is to add an event listener to the assets/stimulus_bootstrap.js file:

// assets/stimulus_bootstrap.js
import { startStimulusApp } from '@symfony/stimulus-bundle';

document.addEventListener('autocomplete:pre-connect', (event) => {
    // TomSelect 2.x + ux-autocomplete 3.x hardcodes score to 1 for remote data,
    // which prevents filtering of previous results. Setting it to null
    // (or deleting it) restores the default scoring/filtering behavior.
    if (event.detail.options.load) {
        delete event.detail.options.score;
    }
});

const app = startStimulusApp();

[zapato]

Before I found this bug report, I used Junie in PHPStorm to try and find a solution. After some work the AI offered the following workaround. I don't know if the reason is correct (see comments in code), but I can confirm that this works for me.

The suggested "fix" is to add an event listener to the assets/stimulus_bootstrap.js file:

// assets/stimulus_bootstrap.js
import { startStimulusApp } from '@symfony/stimulus-bundle';

document.addEventListener('autocomplete:pre-connect', (event) => {
    // TomSelect 2.x + ux-autocomplete 3.x hardcodes score to 1 for remote data,
    // which prevents filtering of previous results. Setting it to null
    // (or deleting it) restores the default scoring/filtering behavior.
    if (event.detail.options.load) {
        delete event.detail.options.score;
    }
});

const app = startStimulusApp();

This approach seems to filter the results list only by that term, without taking other search fields into account:

#[AsEntityAutocompleteField]
class BuildungAutocompleteField extends AbstractType
{
    #[\Override]
    public function configureOptions(OptionsResolver $resolver): void
    {
        $resolver->setDefaults([
            /* Search fields are ignored */
            'searchable_fields' => [
                'name',
                'alternativeName',
                'postalCode',
                'street',
                'houseNo',
            ],
           /* ... */
        ]);
    }

   /* ... */
}

[ehymel]

This approach seems to filter the results list only by that term, without taking other search fields into account:

That is not the behavior I am seeing. I have a similar class with 'searchable_fields' => ['lastName', 'firstName'] that successfully searches on both first and last names.

[zapato]

This approach seems to filter the results list only by that term, without taking other search fields into account:

That is not the behavior I am seeing. I have a similar class with 'searchable_fields' => ['lastName', 'firstName'] that successfully searches on both first and last names.

Are 'lastName' and 'firstName' also shown in the dropdown text?
In my case, the workaround only made it possible to filter the text data displayed in the dropdown menu. Search fields, such as “Street” or “Zip Code,” which are not displayed in the dropdown menu, cannot be filtered using this workaround in my case. Previously, this was possible

[ehymel]

Are 'lastName' and 'firstName' also shown in the dropdown text? In my case, the workaround only made it possible to filter the text data displayed in the dropdown menu. Search fields, such as “Street” or “Zip Code,” which are not displayed in the dropdown menu, cannot be filtered using this workaround in my case. Previously, this was possible

Interesting! Yes, both first and last names are shown in the dropdown text. I don't have any cases matching your scenario.