This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
When i upgrade angular version 1.5.0-rc.2 then it is not working #1422
Comments
|
Please search before creating new issues. Duplicate #1325 Possible workaround: #1325 (comment) |
Narretz
added a commit
to Narretz/ui-select
that referenced
this issue
Feb 12, 2016
In Angular 1.5, transcluded content is linked lazily. For uiSelect that means the clone in the transclude function is not compiled and linked yet, so uiSelect cannot detect the match and choices elements by their classnames, because they haven't been set yet (which happens by replacing the elements with the templates). However, the templateUrl function is executed at this point, so we can use it to add the class names to the directive elements. On another note, this behavior also affected versions earlier than 1.5.0-beta.2, when the template of ui-select-match or ui-select-choices wasn't cached. In that case, the async compilation of the template would mean also that the clone in the transclude function wasn't compiled yet, and so the classes wouldn't be set either. Closes angular-ui#1422 Closes angular-ui#1356 Closes angular-ui#1325 Closes angular-ui#1239
Narretz
added a commit
to Narretz/ui-select
that referenced
this issue
Feb 12, 2016
In Angular 1.5, transcluded content is compiled lazily. For uiSelect that means the clone in the transclude function is not compiled and linked yet, so uiSelect cannot detect the match and choices elements by their classnames, because they haven't been set yet (which happens by replacing the elements with the templates). However, the templateUrl function is executed at this point, so we can use it to add the class names to the directive elements. On another note, this behavior also affected versions earlier than 1.5.0-beta.2, when the template of ui-select-match or ui-select-choices wasn't cached. In that case, the async compilation of the template would mean also that the clone in the transclude function wasn't compiled yet, and so the classes wouldn't be set either. This might be the cause of the error described in issue angular-ui#224. Closes angular-ui#1422 Closes angular-ui#1356 Closes angular-ui#1325 Closes angular-ui#1239
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
angular.js:13307 Error: [ui.select:transcluded] Expected 1 .ui-select-match but got '0'.
at http://test.com:9012/library/ui-select/dist/select.js:125:12
at http://test.com:9012/library/ui-select/dist/select.js:1035:19
at publicLinkFn (http://test.com:9012/bower_components/angular/angular.js:8193:29)
at http://test.com:9012/bower_components/angular/angular.js:8535:29
at boundTranscludeFn (http://test.com:9012/bower_components/angular/angular.js:8332:16)
at controllersBoundTransclude (http://test.com:9012/bower_components/angular/angular.js:9108:20)
at http://test.com:9012/library/ui-select/dist/select.js:1023:9
at invokeLinkFn (http://test.com:9012/bower_components/angular/angular.js:9580:9)
at nodeLinkFn (http://test.com:9012/bower_components/angular/angular.js:9066:11)
The text was updated successfully, but these errors were encountered: