1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
// Copyright 2024 Google LLC
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
/// Callbacks that the wrapping binary can implement.
///
/// These allow you to do stuff like inject telemetry into the daemon
/// or trigger background processes based on a particular session
/// name (for example you could update and re-build a repository n
/// minutes after your `devserver` session disconnects on the assumption
/// that the user is done for the day).
///
/// Hooks are invoked inline within the daemon's control flow, so
/// you MUST NOT block for extended periods of time. If you need to
/// do work that could block for a while, you should spin up a worker
/// thread and enqueue events so the hooks can be processed async.
///
/// It would be nicer if the hooks took `&mut self`, but they are called
/// from an immutable context and it is nice to avoid the syncronization
/// / interior mutability unless it is required. Users can always get
/// mutable state with a cell / mutex.
///
/// Any errors returned will simply be logged.
///
/// All hooks do nothing by default.