| commit | 67b12072c8e05a921324c7cebf3b3cea68f70c9a | [log] [tgz] |
|---|---|---|
| author | Paladox none <thomasmulhall410@yahoo.com> | Thu Mar 27 09:37:48 2025 -0700 |
| committer | Paladox none <thomasmulhall410@yahoo.com> | Fri Mar 28 02:01:23 2025 -0700 |
| tree | 32d95c84f0526db1a9f9e54639be0bc9d68f0726 | |
| parent | 1f3978dd6b038ca07f5514d23689ede3edc94403 [diff] |
Revert "Use json from legacy-modes" This reverts commit 1f3978dd6b038ca07f5514d23689ede3edc94403. The reason why under the moder lang-json that it didn't highlight as well, was because the default theme doesn't highlight everything. For example it doesn't highlight propertyName. We have to create our own theme that highlights it. Change-Id: I4899f5199484d22c317a2e238b132a307e01548b
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.