Skip to content
This repository was archived by the owner on Apr 4, 2025. It is now read-only.

AngularHint triggers its own warnings #52

Open
sjelin opened this issue Nov 13, 2014 · 0 comments
Open

AngularHint triggers its own warnings #52

sjelin opened this issue Nov 13, 2014 · 0 comments

Comments

@sjelin
Copy link

sjelin commented Nov 13, 2014

I created a very simple angular app

<!DOCTYPE html>
<html ng-app ng-hint>
  <head>
    <meta charset="utf-8">
    <title>Angular.js Example</title>
    <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.2.26/angular.min.js"></script>
        <script src="ngHint.js"></script>
  </head>
  <body>
    First name:<input ng-model="firstName" type="text"/>
    <br>
    Last name:<input ng-model="lastName" type="text"/>
    <br>
    Hello {{firstName}} {{lastName}}
  </body>
</html>

This triggered two warnings in Angular Hint:

Angular Hint: Modules ngHint.js:119
    Warning ngHint.js:136
        Module "ngHintScopes" was created but never loaded. ngHint.js:138
Angular Hint: Controllers ngHint.js:119
    Warning ngHint.js:136
        It is against Angular best practices to instantiate a controller on the window. This behavior is deprecated in Angular 1.3.0 ngHint.js:138

Clearly none of this is my app's fault. In particular, I was definitely not the one who created ngHintScopes, and further it really should be loaded.
@sjelin sjelin changed the title AngularHint creates its own warnings AngularHint triggers its own warnings Nov 13, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sjelin