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
{{ message }}
This repository was archived by the owner on Oct 2, 2019. It is now read-only.
Would you be willing to consider a PR for an onBeforeSelect callback? This would provide a way to access both the selection and the current value, potentially aborting the selection. If you try to track this externally it can get complicated (mostly due to assumptions about the target model's behavior) but the internal solution is fairly simple.
Implementation would include a check for a $q promise property and complete the selection when the promise is resolved or abort the selection in the case of a reject. (Without the promise, selection would be aborted via a falsey return value.)
The text was updated successfully, but these errors were encountered:
when selecting a item, the item should select or not , which depends on some conditions. In another word, when not satisfy some conditions it keeps original selected item.
I know ui-select have an event named 'on-select', but it is the 'after selected callback'
I wonder where I should add the callback in the select.js?
This sounds like a poor direction to go on - this is probably an indication that something else might be missing, as adding config to override config can only spiral.
Would you be willing to consider a PR for an onBeforeSelect callback? This would provide a way to access both the selection and the current value, potentially aborting the selection. If you try to track this externally it can get complicated (mostly due to assumptions about the target model's behavior) but the internal solution is fairly simple.
Implementation would include a check for a $q promise property and complete the selection when the promise is resolved or abort the selection in the case of a reject. (Without the promise, selection would be aborted via a falsey return value.)
The text was updated successfully, but these errors were encountered: