gerrit/Documentation/dev-plugin-pg-styling.txt
Viktar Donich 9bd0ce688d Make metadata sections configurable from plugin
For plugins, imported with HTML imports, and providing CSS modules, use
provided styles to control metadata sections in gr-change-view.

Related Polymer API:
https://www.polymer-project.org/1.0/docs/devguide/styling#custom-style

Includes sample integration test.

Sample code for using proposed API, in plugin.js:

Gerrit.install(function(plugin) {
  plugin.registerStyleModule('change-metadata', 'my-plugin-style');
});

Please note that `my-plugin-style` has to be unique, so plugin name
should be included.

Sample code for using proposed API, in myplugin.html:

<dom-module id="my-plugin-style">
  <template>
    <style>
      :root {
        --change-metadata-assignee: {
          display: none;
        }
        --change-metadata-label-status: {
          display: none;
        }
        --change-metadata-strategy: {
          display: none;
        }
        --change-metadata-topic: {
          display: none;
        }
      }
    </style>
  </template>
</dom-module>

Feature: Issue 5402
Change-Id: Iba2645f28d5b411df2d0310a05aa0cbec4cca26a
2017-04-25 17:27:13 -07:00

62 lines
2.2 KiB
Plaintext

= Gerrit Code Review - PolyGerrit Plugin Styling
CAUTION: Work in progress. Hard hat area. +
This document will be populated with details along with implementation. +
link:https://groups.google.com/d/topic/repo-discuss/vb8WJ4m0hK0/discussion[Join the discussion.]
== Plugin styles
Plugins may provide link:https://www.polymer-project.org/2.0/docs/devguide/style-shadow-dom#style-modules[Polymer style modules] for UI CSS-based customization.
PolyGerrit UI implements number of styling endpoints, which apply CSS mixins link:https://tabatkins.github.io/specs/css-apply-rule/[using @apply] to its direct contents.
NOTE: Only items (ie CSS properties and mixin targets) documented here are guaranteed to work in the long term, since they are covered by integration tests. +
When there is a need to add new property or endpoint, please link:https://bugs.chromium.org/p/gerrit/issues/entry?template=PolyGerrit%20Issue[file a bug] stating your usecase to track and maintain for future releases.
Plugin should be html-based and imported following PolyGerrit's link:dev-plugins-pg.html#loading[dev guide].
Plugin should provide Style Module, for example:
``` html
<dom-module id="some-style">
<style>
:root {
--css-mixin-name: {
property: value;
}
}
</style>
</dom-module>
```
Plugin should register style module with a styling endpoint using `Plugin.prototype.registerStyleModule(endpointName, styleModuleName)`, for example:
``` js
Gerrit.install(function(plugin) {
plugin.registerStyleModule('some-endpoint', 'some-style');
});
```
== Available styling endpoints
=== change-metadata
Following custom css mixins are recognized:
* `--change-metadata-assignee`
+
is applied to `gr-change-metadata section.assignee`
* `--change-metadata-label-status`
+
is applied to `gr-change-metadata section.labelStatus`
* `--change-metadata-strategy`
+
is applied to `gr-change-metadata section.strategy`
* `--change-metadata-topic`
+
is applied to `gr-change-metadata section.topic`
Following CSS properties have link:https://gerrit.googlesource.com/gerrit/+/master/polygerrit-ui/app/elements/change/gr-change-metadata/gr-change-metadata-it_test.html[long-term support via integration test]:
* `display`
+
can be set to `none` to hide a section.