-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Bug fix preventing errors when using async resources #259
Conversation
To prevent the hash to reload the page
Can you rebase and remove /dist files? |
Is this PR ready to merge? I run into this problem on a daily basis. It's very cumbersome. |
is this fixed? I'm getting the same error using the result of a $resource |
I'm getting the same issues, here's a simple example: |
Figured out the repeater error / 'Can't Interpolate bug'. |
@justsml Can you show where did you apply the fix? |
@hatpick
And now, fixed code:
In JADE
|
@justsml I did not have that issue with my html. Still having tons of errors in the console. |
I still get similar errors. The weird thing with dynamically loaded ui-select, is that it works after it has loaded once, but the first initiation, after clearing the cache fails.
The Url decoded means: http://errors.angularjs.org/1.4.0-beta.4/ui.select/transcluded?p0=Expected 1 .ui-select-match but got '{0}'.&p1=0 Side note: doesn't work with any of the recent angular versions, 1.3.x - 1.4.x |
If the select directive is supplied a resource promise (such as the $resource class from angular itself) a series of errors are occur when the library initialises. The following errors occur if the ui-select-choices directive is given a repeat expression using a $resource result;
I've added some additional checks which prevent the uninitialised variables from being used, resolving the issue altogether :)
Note: my work is based on a fork of @juanpasolano's fork, so it also includes his patches in #198