tree: 237fdb3af52c0660d55ddb760a464b78d8a9d92c [path history] [tgz]
  1. Makefile
  2. README.md
  3. bin/
  4. go/
  5. images/
  6. modules/
  7. package-lock.json
  8. package.json
  9. pages/
  10. tsconfig.json
  11. tslint.json
  12. webpack.config.ts
bugs-central/README.md

Bugs Central

Skia has many clients (eg: Android, Flutter native+web, Chromium, Skia itself), those clients use different issue trackers and different queries within those trackers.

Bugs central keeps track of Skia bugs in Skia's major clients + issue trackers.

Design doc is here.

Working on the lit-html frontend

Bugs Central follows the pulito model of organization and uses webpack to bundle the pages together.

To get started, run npm ci in the top bugs-central directory. You won't need to run this very often - only when deps are rolled forward.

The lit-html pages are in ./pages. These are very simple, as they compose more complex modules found in ./modules. To access the demo pages for the modules, run

    make serve

Then open a web browser to localhost:8080/static/[module].html. These demo pages have some mock data (piped in via a mock-fetch) and are good proxies for working with real data from a real web server.

The pages in ./pages also show up at localhost:8080/static/[page].html although these won‘t be as interesting as there is no mock data and you may see strange artifacts like {{.Title}} as that’s where the golang templating on the server will insert data.