--To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/IZ4r9xSmDoEJ.
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To post to this group, send email to ang...@googlegroups.com.
To unsubscribe from this group, send email to angular+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/angular?hl=en.
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/e8049tlrRrYJ.
Well - that broke pretty much all my directives. On the plus side, fixing them was easy, and the changes have removed some of the hoops I'd had to jump through previously to get certain directives working properly.It feels a lot more seamless now - before, I was getting some confusing issues relating to isolate scopes, especially mixing my directives with ng-repeat. It's early days, but so far as I can tell, all these issues seem to have vanished.Great job.
One question though - are we to expect a many more potentially breaking changes as we progress? I'm a little surprised to be getting these during the RC phase.
Directive controllers are still injectable, just as regular controllers, but you can't inject attribute values or accessors into them. This was a very obscure feature that was causing only problems and with introducing the two-way data-binding between parent and isolate scope it wasn't feasible to preserve it. If you do have real need for this feature then let us know and we'll help you use a better way to solve the same use case.
/i
On Mon, Jun 11, 2012 at 12:27 PM, rur
"the inject option for the directive controller injection was removed"
Does this mean that directive controllers will no longer be injectable with services?
On Monday, 11 June 2012 01:07:29 UTC-7, Igor Minar wrote:Hi guys,I just pushed the last planned 1.0 RC!Announcement: http://goo.gl/L1EL0cheers,Igor
--To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/e8049tlrRrYJ.
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To unsubscribe from this group, send email to angular+unsubscribe@googlegroups.com.
Igor,I'm experiencing the same issue. All backslashes are being escaped. Angular-seed has the same issue.Clicking view1 changes the url to:- Kyle
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/bdJwu5Jd_MwJ.
I want this too!right now, without isolated scope, getter is easy var val=$scope.$eval(attr.whatever)but setter is not exposed.
On Monday, June 11, 2012 5:06:07 PM UTC-7, ItsLeeOwen wrote:Hi Igor, regarding the removal of injecting attribute values/accessors, is it possible to have a widget that is given scope values/accessors, and does not create an isolated scope?
On Monday, June 11, 2012 1:08:10 PM UTC-7, Igor Minar wrote:Directive controllers are still injectable, just as regular controllers, but you can't inject attribute values or accessors into them. This was a very obscure feature that was causing only problems and with introducing the two-way data-binding between parent and isolate scope it wasn't feasible to preserve it. If you do have real need for this feature then let us know and we'll help you use a better way to solve the same use case./i
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To view this discussion on the web visit https://groups.google.com/d/msg/angular/-/TmcglNyir6MJ.