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
I'm assigning a user to the view, which Angular, through some black magic, handles, however when I use angular-xeditable to change the value, the original value is preserved, and my edit is lost.
No 'onbeforesave' or 'onaftersave' callback fires, so I can't intercept the save attempt and return a wrapped promise with the updated value.
I'm not gonna lie, I have no idea how this should be fixed, but, as Angular supports passing promises directly to views, I figured it was worth documenting this at least.
The text was updated successfully, but these errors were encountered:
editable-empty class still applied even if promise resolved with non-empty value. I'll fix it in 0.1.5.
status not shown correctly when using showStatus() method. It's because inside used direct access to $scope.user.status that is pormise and cannot be accessed directly (in fact, value is in $scope.user.$$v ).
The solution is to put expression right into template - then angular will resolve everything automatically, see my fiddle third sample:
Check out this JSFiddle - http://jsfiddle.net/pP2jZ/1/
I'm assigning a user to the view, which Angular, through some black magic, handles, however when I use angular-xeditable to change the value, the original value is preserved, and my edit is lost.
No 'onbeforesave' or 'onaftersave' callback fires, so I can't intercept the save attempt and return a wrapped promise with the updated value.
I'm not gonna lie, I have no idea how this should be fixed, but, as Angular supports passing promises directly to views, I figured it was worth documenting this at least.
The text was updated successfully, but these errors were encountered: