-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onChange should only trigger by user action #198
Comments
Similar issue here. onChange shouldn't trigger when the bound value is set externally |
I'm running into the same issue. In this case I'm using Happy to put a PR together if there's appetite from the maintainer for this change, @pstanoev? In the meantime I've found a workaround for my issue using <AutoComplete
beforeChange={(oldItem, newItem) => {
filter.selectedCountry = newItem;
dispatch('change');
}}
bind:selectedItem={filter.selectedCountry}
items={filter.countryOptions}
labelFieldName="name"
valueFieldName="iso_code"
/> The call to |
Part of the problem is also in this issue : #36 |
In my opinion onChange shoud not be trigger by a external assignment, only when user manually change the field
This special case that is causing me trouble :
I need to persist the object in DB when user change the value, then the value gets update from the DB, but it's triggering a onChange event causing a recursive loop ...
The text was updated successfully, but these errors were encountered: