Closed ayackel closed 9 years ago
Looks like a duplicate of #159 and at least one other that I saw today.
@Splaktar It's not only about disabling specific messages but about disabling angular-hint itself. The runtime error means that we can't use Batarang with apps built with ui-router.
There are two separate issues here:
The first is more important to me. Can anyone please provide a reproduction via jsbin, plnkr.co, or jsfiddle that shows ui-router broken by the latest Batarang (v0.7.3)?
I just ran a number of tests with my app (which uses ui-router) and Batarang 0.7.4 enabled. I did not see any exceptions or other issues in the console or with the behavior of my app or routing.
We are using ui-view
but we are not using ng-grid
. So perhaps this is fixed or specific to ng-grid?
Batarang works with UI-Router now.
Can we have a way to disable hints? Angular-hint has some hard-coded directive types that are incompatible with ui-router. My app fails to load because ng-grid cannot find it's controller in the scope. With batarang disabled it is in the scope. I think this is due to the use of 'ui-view' instead of 'ng-view'.