| commit | 331d1728d9a74fa9cdffbba3c85645a36419eff6 | [log] [tgz] |
|---|---|---|
| author | Paladox none <thomasmulhall410@yahoo.com> | Thu Mar 27 17:35:32 2025 -0700 |
| committer | Paladox none <thomasmulhall410@yahoo.com> | Wed Apr 02 08:27:21 2025 -0700 |
| tree | 2893efabea5b1508159cb4856689bf097e6d3be7 | |
| parent | 67b12072c8e05a921324c7cebf3b3cea68f70c9a [diff] |
Create a gerrit theme for CodeMirror It highlights more. To name one it does extra with is propertyName. It also tries to align with what we do for highlight.js. Depends-On: Ibf3b98ff6a3f2edf093bf212b5f96bc4ef315547 Change-Id: Ie2873fece99f755805afa915fe1f052d531797ed
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.