Last active
November 5, 2024 18:59
-
-
Save JasonKleban/50cee44960c225ac1993c922563aa540 to your computer and use it in GitHub Desktop.
TypeScript LiteEvent Events implementation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
interface ILiteEvent<T> { | |
on(handler: { (data?: T): void }) : void; | |
off(handler: { (data?: T): void }) : void; | |
} | |
class LiteEvent<T> implements ILiteEvent<T> { | |
private handlers: { (data?: T): void; }[] = []; | |
public on(handler: { (data?: T): void }) : void { | |
this.handlers.push(handler); | |
} | |
public off(handler: { (data?: T): void }) : void { | |
this.handlers = this.handlers.filter(h => h !== handler); | |
} | |
public trigger(data?: T) { | |
this.handlers.slice(0).forEach(h => h(data)); | |
} | |
public expose() : ILiteEvent<T> { | |
return this; | |
} | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
class Security{ | |
private readonly onLogin = new LiteEvent<string>(); | |
private readonly onLogout = new LiteEvent<void>(); | |
public get LoggedIn() { return this.onLogin.expose(); } | |
public get LoggedOut() { return this.onLogout.expose(); } | |
// ... onLogin.trigger('bob'); | |
} | |
function Init() { | |
var security = new Security(); | |
var loggedOut = () => { /* ... */ } | |
security.LoggedIn.on((username?) => { /* ... */ }); | |
security.LoggedOut.on(loggedOut); | |
// ... | |
security.LoggedOut.off(loggedOut); | |
} |
What is the point of having it private, then having an
expose
method which returns the instance? Why not make it public from the beginning?
It was an effort to discourage it from being written to. There are probably better ways these days if such control is needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for this!
The way functions are typed are confusing to me, plus the repeated type definitions:
Here is my take on it, dropping expose(can be added back in for those who need it):