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
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
Now that we've switched to an event emitter, log was no longer used and was causing confusion.
The major change here is that once we emit an event, it is not stored. If this turns out to be a big deal, we can implement a message storage module.
Closes#81
tweaked test
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -225,12 +225,11 @@ The following steps describe how an AngularHint module should be developed.
225
225
- Each AngularHint module should load its own dependencies using `browserify`. For instance, AngularHintDOM depends on the library `domInterceptor`. This dependency is included within AngularHintDom by the browserify `require` function.
226
226
- All AngularHint modules should load AngularHintLog as a dependency, see #3.
227
227
228
-
3. Message Logging
228
+
3. Events
229
229
230
-
All AngularHint modules should use AngularHintLog to log their messages. This creates a standard pipeline for
231
-
all AngularHint messages.
230
+
All AngularHint modules should use `hint.emit` to emit their events. This creates a standard pipeline for all AngularHint events.
232
231
233
-
To use AngularHintLog, see its [README.md](https://github.com/angular/angular-hint-log#angular-hint-log).
232
+
`angular.hint` is an instance of [EventEmitter2](https://github.com/asyncly/EventEmitter2).
0 commit comments