| commit | 3afc9b32d26c761d67b21256792720d5c8916b43 | [log] [tgz] |
|---|---|---|
| author | paladox <thomasmulhall410@yahoo.com> | Mon Apr 15 21:36:30 2024 +0100 |
| committer | Paladox none <thomasmulhall410@yahoo.com> | Mon Apr 15 21:23:11 2024 +0000 |
| tree | c0e352383a4e8d73663f408c6ab49f9c4d88865c | |
| parent | d4f9247d3efb6a0e461af701986235511d05b7e3 [diff] |
Use new go and yaml codemirror packages Migrates from legacy mode. Depends-On: Ic3990638f96872c72d5acb4bcb7a1a1f163ce085 Change-Id: I6a7c0d29fbc44cc7bc76ad86bcd4678ac0330dac
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.