Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support for ui-router resolve, onEnter and onExit #54
Since ui-router of the angular-ui project is quickly becoming the de-facto replacement of Angular's routeProvider, it would be good to have full support for it. This means that the 'resolve', 'onEnter' and 'onExit' properties in $stateProvider.state() should be handled by ngmin.
Took me awhile to figure out that this was where my minified code was going bust.
Does anyone have any stop-gap solution for converting the standard form of these functions, i.e.
To a minification safe form?
Apologies if this is a noob type question!
referenced this issue
Mar 15, 2014
added a commit
May 13, 2014
@donaldpipowitch That link shows which 24 open ngmin issues that just work in ng-annotate. In addition, there are 6 open ngmin issues that work in ng-annotate with a workaround. See full annotated issue list.
But Instead of just looking at that list I recommend reading the more elaborate comparison I wrote yesterday in issue #93 - The future of ngmin and ng-annotate. @kikonen-fiksu: That comparison also describes where ng-annotate is trailing ngmin, in particular not as extensive tooling integration (although Grunt, Browserify, Brunch and Gulp is there so far and more is coming). Q: "does ng-annotate have rails assets pipeline integration?" A: "not currently, but hopefully very soon". It should be a 30 minute job for a rails/ruby/gem savvy person to create it.
Would this be a result of