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 May 29, 2019. It is now read-only.
when defining your query scope method for typeahead, if you name it "query()" and call this from your typeahead as so:
<input type="text" ng-model="selected" typeahead="n.name for n in query($viewValue)">
The query method will never get called. Since "match" is never set and remains 'undefined', therefore attempt to call length() on undefined error. If name scope can't be protected from the calling scope, I would suggest that this be documented since the code comments state that 'match', 'query'... are grouped as to not pollute the scope, which is a little misleading.
AngularJS 1.1.3
ui-bootstrap-tpls: 0.6.0
The text was updated successfully, but these errors were encountered:
@alank64 this was a real bug with scopes collision, it is fixed in master now, will be part of the next release. Thnx for taking time to report this one.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
when defining your query scope method for typeahead, if you name it "query()" and call this from your typeahead as so:
The query method will never get called. Since "match" is never set and remains 'undefined', therefore attempt to call length() on undefined error. If name scope can't be protected from the calling scope, I would suggest that this be documented since the code comments state that 'match', 'query'... are grouped as to not pollute the scope, which is a little misleading.
AngularJS 1.1.3
ui-bootstrap-tpls: 0.6.0
The text was updated successfully, but these errors were encountered: