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 has been archived by the owner on Oct 2, 2019. It is now read-only.
you guys recently checked in a fix that when the model of a multiSelect component has changed, so refreshComponent will be called. Here: #1243
BUT:
It would be very nice if the refreshComponent would call a ngChange method. I.e. as a configurable directive attribute where we cann pass our pointer of method, which concrete method will be called.
@oezkany I've merged in #1243 and it will land in the next release. However, we are not keen on adding a plethora of directive attributes to the project. I would love to see a PR that refactors the the directive away from having a million attributes and instead accepting a config object.
Hi,
you guys recently checked in a fix that when the model of a multiSelect component has changed, so refreshComponent will be called. Here: #1243
BUT:
It would be very nice if the refreshComponent would call a ngChange method. I.e. as a configurable directive attribute where we cann pass our pointer of method, which concrete method will be called.
Example:
The text was updated successfully, but these errors were encountered: