| commit | da5849b46651a8f72d520810736b38b63ec0d010 | [log] [tgz] |
|---|---|---|
| author | Paladox none <thomasmulhall410@yahoo.com> | Sat Jan 31 05:14:23 2026 -0800 |
| committer | Paladox none <thomasmulhall410@yahoo.com> | Sat Jan 31 05:15:21 2026 -0800 |
| tree | a69c69ba21fab9c2879f3da4b62d9cd9e6f7fe9c | |
| parent | a6d0469b9cab54336c985ddc967cbca3407f2aeb [diff] |
Use jinja from @codemirror/lang-jinja instead of legacy mode Depends-On: I1409d4d59e191b7ea04731f3679ecc9a8240abcf Change-Id: I3a7dcbd3b164be42602cde1e0e0e321c783ff87a
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.