-
Notifications
You must be signed in to change notification settings - Fork 62
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
Editorial: Add event definition for 'close' #384
Conversation
A reference to a 'close' event turned into a link back in d2bc4db but there wasn't a local definition - it ended up linking into HTML! This is now triggering a Bikeshed warning - yay! Add a minimal local definition for the event type, like the others.
@asutherland could you take a quick look? |
Co-authored-by: Brett Zamir <[email protected]>
Thanks @brettz9 ! |
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.
This seems fine descriptively. Presumedly, there is text elsewhere in the spec that queues a task to fire the event using the right task source?
The task source integration could be tightened up; there's just a generic declaration that everything happens using the database access task source. Firing of the event happens in close a database connection |
SHA: e196c63 Reason: push, by @inexorabletash Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
A reference to a 'close' event turned into a link back in d2bc4db but
there wasn't a local definition - it ended up linking into HTML! This
is now triggering a Bikeshed warning - yay!
Add a minimal local definition for the event type, like the others.
(No normative behavior changes, no tests required.)
Preview | Diff