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
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
|
= Gerrit Code Review - JavaScript Plugin Endpoints
This document describes Gerrit JavaScript plugin endpoints that you can hook
into for customizing the UI. It is assumed that you are familiar with
link:pg-plugin-dev.html#loading[the general dev guide].
You can either hook into an endpoint by calling `plugin.hook(endpoint)` and
then interact with the returned `HookApi`, which has `onAttached(callback)` and
`onDetached(callback)` methods.
Or you can define a
link:https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements[Web Component,role=external,window=_blank]
and register it directly using
`plugin.registerCustomComponent(endpoint, elementName)`.
Sample code for using an endpoint:
``` js
Gerrit.install(plugin => {
const endpoint = 'change-metadata-item';
plugin.hook(endpoint).onAttached(element => {
const el = element.appendChild(document.createElement('div'));
el.textContent = 'Ah, there it is. Lovely.';
el.style = 'background: pink; line-height: 4em; text-align: center;';
});
});
```
== Default parameters
All endpoints receive the following parameters, set as attributes to custom
components that are instantiated at the endpoint:
* `plugin`
+
the current plugin instance, the one that is used by `Gerrit.install()`.
* `content`
+
decorated DOM Element, is only set for registrations that decorate existing
components.
== Plugin endpoints
The following endpoints are available to plugins.
=== banner
The `banner` extension point is located at the top of all pages. The purpose
is to allow plugins to show outage information and important announcements to
all users.
=== change-view-integration
The `change-view-integration` extension point is located between `Files` and
`Change Log` section on the change view page, and it may take full page's
width.
* `change`
+
current change displayed, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `revision`
+
current revision displayed, an instance of
link:rest-api-changes.html#revision-info[RevisionInfo]
=== change-metadata-item
The `change-metadata-item` extension point is located on the bottom of the
change view left panel, under the `Label Status` and `Links` sections. Its width
is equal to the left panel's, and its primary purpose is to allow plugins to add
sections of metadata to the left panel.
In addition to default parameters, the following are available:
* `change`
+
current change displayed, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `revision`
+
current revision displayed, an instance of
link:rest-api-changes.html#revision-info[RevisionInfo]
* `labels`
+
labels with scores applied to the change, map of the label names to
link:rest-api-changes.html#label-info[LabelInfo] entries
=== check-result-expanded
The `check-result-expanded` extension point is attached to a result
of the link:pg-plugin-checks-api.html[ChecksAPI] when it is expanded. This can
be used to attach a Web Component displaying results instead of the
`CheckResult.message` field which is limited to raw unformatted text.
In addition to default parameters, the following are available:
* `result`
+
The `CheckResult` object for the currently expanded result row.
* `run`
+
Same as `result`. The `CheckRun` object is not passed to the endpoint.
The end point contains the `<gr-formatted-text>` element holding the
`CheckResult.message` (if any was set).
=== robot-comment-controls
The `robot-comment-controls` extension point is located inside each comment
rendered on the diff page, and is only visible when the comment is a robot
comment, specifically if the comment has a `robot_id` property.
In addition to default parameters, the following are available:
* `comment`
+
current comment displayed, an instance of
link:rest-api-changes.html#comment-info[CommentInfo]
=== repo-command
This endpoint is situated among the repository commands.
In addition to default parameters, the following are available:
* `repoName`
+
String name of the repository currently being configured.
* `config`
+
The object representing the repo config.
=== repo-config
The `repo-config` extension point is located at the bottom of the repository
configuration settings screen.
In addition to default parameters, the following are available:
* `repoName`
+
String name of the repository currently being configured.
* `readOnly`
+
Boolean whether the repository configuration is read only by the logged in user.
=== settings-menu-item
This endpoint is situated at the end of the navigation menu in the settings
screen.
=== settings-screen
This endpoint is situated at the end of the body of the settings screen.
=== profile
This endpoint is situated at the top of the Profile section of the settings
screen below the section description text.
=== reply-text
This endpoint wraps the textarea in the reply dialog.
=== reply-label-scores
This endpoint decorator wraps the voting buttons in the reply dialog.
=== header-title
This endpoint wraps the title-text in the application header.
=== cherrypick-main
This endpoint is located in the cherrypick dialog. It has two slots `top`
and `bottom` and `changes` as a parameter with the list of changes (or
just the one change) to be cherrypicked.
=== confirm-revert-change
This endpoint is inside the confirm revert dialog. By default it displays a
generic confirmation message regarding reverting the change. Plugins may add
content to this message or replace it entirely.
=== confirm-submit-change
This endpoint is inside the confirm submit dialog. By default it displays a
generic confirmation message regarding submission of the change. Plugins may add
content to this message or replace it entirely.
In addition to default parameters, the following are available:
* `change`
+
The change beinng potentially submitted, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `action`
+
The submit action, including the title and label, an instance of
link:rest-api-changes.html#action-info[ActionInfo]
=== commit-container
The `commit-container` extension point adds content at the end of the commit
message to the change view.
In addition to default parameters, the following are available:
* `change`
+
current change displayed, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `revision`
+
current revision displayed, an instance of
link:rest-api-changes.html#revision-info[RevisionInfo]
== Dynamic Plugin endpoints
The following dynamic endpoints are available to plugins by calling
`plugin.registerDynamicCustomComponent(endpoint, elementName)`.
=== change-list-header
The `change-list-header` extension point adds a header to the change list view.
=== change-list-item-cell
The `change-list-item-cell` extension point adds a cell to the change list item.
In addition to default parameters, the following are available:
* `change`
+
current change of the row, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
=== change-view-tab-header
The `change-view-tab-header` extension point adds a primary tab to the change
view. This must be used in conjunction with `change-view-tab-content`.
In addition to default parameters, the following are available:
* `change`
+
current change displayed, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `revision`
+
current revision displayed, an instance of
link:rest-api-changes.html#revision-info[RevisionInfo]
=== change-view-tab-content
The `change-view-tab-content` extension point adds primary tab content to
the change view. This must be used in conjunction with `change-view-tab-header`.
In addition to default parameters, the following are available:
* `change`
+
current change displayed, an instance of
link:rest-api-changes.html#change-info[ChangeInfo]
* `revision`
+
current revision displayed, an instance of
link:rest-api-changes.html#revision-info[RevisionInfo]
=== account-status-icon
The `account-status-icon` extension point adds an icon to all account chips and
labels.
In addition to default parameters, the following are available:
* `accountId`
+
the Id of the account that the status icon should correspond to.
|
