-
Notifications
You must be signed in to change notification settings - Fork 885
chore(site): add storybook for terminal page #12441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…r-web-term-notifications
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!!!
|
||
// Runs when the last event listener is added | ||
clearTimeout(callEventsDelay); | ||
callEventsDelay = window.setTimeout(() => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, why do we need the timeout? I think it makes sense since it allows us to make sure all the listeners are hooked up first but was there a bug with how it was before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the problem with the previous implementation is that it did not respect the order of the events so if the error
listener was defined before it would call it first even if it was the third event in the list for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohhhhh I see! Makes sense.
Co-authored-by: Asher <ash@coder.com>
No description provided.