T252798: How should hook implementations access the current request context?
From cpt
| Phabricator Link | T252798 |
|---|---|
| Status | resolved |
| Priority | Medium (orange) |
| Points | |
| Phabricator Task Created | 2020/05/14 12:34 PM |
| Wiki Page Created | 2020/05/14 01:11 PM |
| Phabricator Task Last Modified | 2021/02/25 05:33 PM |
| Wiki Page Last Updated | 2021/02/25 07:24 PM |
| Phabricator Task Closed | 2020/05/28 06:27 PM |
| Authored By | dbarratt (David Barratt) |
| Assigned To | tstarling (Tim Starling) |
| Projects |
|
| Platform Engineering Initiative Column | New Hook System |
| Platform Team Workboards Column | |
| Subtasks | |
| Parent Tasks |
Column Transitions: (Added project: ⇑, Removed project: ⇓,Entered column: ⇒, Exited column: ⇐)
| Project | Column | Date |
|---|---|---|
| ⇑ Platform Engineering | 14 May 2020 | |
| ⇑ TechCom | 14 May 2020 | |
| ⇑ Anti-Harassment | 14 May 2020 | |
| Platform Engineering | ⇐ Inbox | 15 May 2020 |
| Platform Engineering | ⇒ Triage Meeting Inbox | 15 May 2020 |
| ⇓ Platform Engineering | 19 May 2020 | |
| ⇑ Platform Team Initiatives (New Hook System) | 19 May 2020 | |
| TechCom | ⇐ Inbox | 26 May 2020 |
| TechCom | ⇒ Watching | 26 May 2020 |
