onSearchChange triggered by OptionSubmit and by Blur on Selects

[1Baldasso]

In our project, we handle all the search logic in the api, so we dont need filtering and anything else.
In this case, we have been using onSearchChange to trigger the search logic.
But we ran into a issue in which anytime we select an option, a search is triggered with the selected label as searchValue, and also when on blur, another search is dispatched as empty. Since in these cases the options are filtered, in cases which the label is not directly related to the selected value label we are getting an empty field but with the correct value set on the form.

Is there a way to disable the onSearchChange to be triggered on those cases? Is there a possible solution for our problem besides creating a custom select directly from ComboBox?

We are using an uncontrolled form

[rtivital]

Mantine does not provide any props to customize this behavior, you can do that either in your search function or create a custom component with Combobox.

[1Baldasso]

Is there any parameter coming from the search function in which we could know if the caller was onChange or any other?

[rtivital]

No, there is no such parameter

[1Baldasso]

Thanks!

[1Baldasso]

Hello @rtivital!
We ended up creating a copy of the base select in which we added a prop that can personalize this behavior.
I dont know if that can be useful, but if it is I can create a Feature Request and Submit the PR.

Best Regards.

[rtivital]

It is the intended usage of Combobox component – if the default Mantine component does not satisfy your requirements, you can easily create a new component for your application. It keeps Select and other components API simple and easier to maintain.

[danierdev]

Hello @rtivital! We ended up creating a copy of the base select in which we added a prop that can personalize this behavior. I dont know if that can be useful, but if it is I can create a Feature Request and Submit the PR.

Best Regards.

Would you mind sharing your implementation 🙏, I'm having the same issue