Skip to content

onSearchComplete triggers after onSelect when only one match exists #852

@diegosps

Description

@diegosps

When the behavior described in #846 happens (only one suggestion with exact match), the order of the events are swapped.

For example, if I have logic the does some cleanup at search complete and do some processing at select, whenever I click in an already filled input, I always end up with a clear state because onSearchComplete triggers after the onSelect event.

I can do some checks to avoid the cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions