tag | a4b73b52cf8614ad692b5a03adfc14ca0ff05931 | |
---|---|---|
tagger | Luca Milanesio <luca.milanesio@gmail.com> | Mon Apr 17 11:04:09 2023 +0000 |
object | 1a7835bdfa55d60c717bad20b943e34499da0016 |
v3.8.0-rc2
commit | 1a7835bdfa55d60c717bad20b943e34499da0016 | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Mon Mar 27 12:47:55 2023 +0200 |
committer | Ben Rohlfs <brohlfs@google.com> | Mon Mar 27 12:47:55 2023 +0200 |
tree | ad15192eb64577c2951e4ecd047d14782cc94edb | |
parent | 597573b5d1ed44c75844d2b8047aae08f7ef8619 [diff] |
Fix CodeMirror in dark mode Release-Notes: skip Google-Bug-Id: b/274854578 Change-Id: Ie6dbebae79441e9813a2993541994a2db44de1cb
A plugin that uses CodeMirror to provide a rich code editing experience in PolyGerrit.
The plugins hooks into the editor
endpoint and registers gr-editor
for it.
The codemirror-element
using CodeMirror is loaded lazily from another js bundle, because it is fairly large, and we don't want to load the large bundle, if the user is not editing anything.
We are using the generic test target in the plugins/
folder. See plugins/BUILD
for how to enable the tests and then run bazel run plugins:web-test-runner
.
For testing you can use FE dev helper (https://gerrit.googlesource.com/gerrit-fe-dev-helper/). It allows you to redirect to (symlinks to) your locally built files. You can use npm run start
to serve files and put the locally built files (or symlinks) in the polygerrit-ui/app/
folder.