22 Commits

Author SHA1 Message Date
Wyatt Allen
744045d542 Add PolyLint Bazel rule
To install the linter:
  npm install -g polylint

To run the linter:
  bazel test //polygerrit-ui/app:polylint_test

Change-Id: I552f6eedce0e4e90d394acfc516940a8c26e948f
2017-05-24 16:53:54 +00:00
Paladox none
722987a7ab PolyGerrit: Update docs on install nodejs 6
nodejs 4 is no longer supported in polymer.

See https://github.com/Polymer/web-component-tester/blob/master/CHANGELOG.md#600---2017-05-15

Which is causing failures for ci. Lets update to nodejs 6.

Change-Id: Ie0e314785e5672e9f557e63c76616d33f601fe24
2017-05-24 00:51:29 +00:00
Kasper Nilsson
2515a1e24f Add some useful commands to Polygerrit's readme
Change-Id: I5d3a3ff295e329fe818e974f6b72cd84a1877c61
2017-05-12 11:31:44 -07:00
Dave Borowitz
9ba270233b PG docs: Add missing step to set up Safari
Change-Id: Idaea3aba2c5ca7e0736272e064c3d836d8181707
2017-05-09 10:29:32 -04:00
Kasper Nilsson
4a03e36aab Add ESLint config & update documentation
Change-Id: I10ecba3272265aa1d6cae29c17f60b2f741f15f4
2017-05-03 11:15:48 -07:00
Han-Wen Nienhuys
2af13fa21d Fix example polygerrit-ui command-line
java should be invoked from $(bazel info output) root. There is no
guarantee that $(which java) is compatible with the JDK that bazel
uses.

Change-Id: I339e4011fd2c84d2e8dd3d4e66730159ca625bbb
2017-04-25 12:37:54 +02:00
David Pursehouse
fb97e86963 polygerrit: Add note in README about running tests in Safari
Change-Id: Ie2da0221f2779a5d035e4062129ae696d254344f
2017-03-30 23:26:38 +00:00
Viktar Donich
805c893c45 Fix polygerrit.war path when building PolyGerrit with Bazel
Change-Id: Ic6bce6ec37fc3059c9bf46e9017393f4721b367e
2017-01-23 14:38:00 -08:00
David Ostrovsky
fdbfcad77d Remove Buck based build
Bug: Issue 5302
Change-Id: I6e860446ef30ff0ad1c7c49fc0e39d39d921820b
2017-01-23 12:44:58 +00:00
Han-Wen Nienhuys
9746c95759 bazel: wct tests.
Change-Id: I297312db715a0b8ca9b540ed4470e54a6b645592
2016-11-03 13:03:03 +01:00
Aaron Gable
5fdd63cded A tiny fix to the polygerrit ui README
Change-Id: Ice481b27482c9c67b9e0206bff4f39f7371e50e2
2016-10-10 16:06:45 -07:00
Orgad Shaneh
dcb574ce8e PolyGerrit: Fix link in README
Change-Id: I551d927a0ac1991b6b4d784e8ac0380e95019501
2016-09-22 11:35:47 +03:00
Andrew Bonventre
9d8447b470 Update PolyGerrit dev README.md
Change-Id: I4fce9749faa72b7cae5a2b6754d1f8b3b24b8e87
2016-08-01 12:16:57 -04:00
Han-Wen Nienhuys
ceb5db093e PolyGerrit: explain how to run a single test file.
Change-Id: Ie3bd69af72560db5a34351d4f25fa779e52da2a1
2016-04-01 11:36:29 -04:00
Eryk Szymanski
d08bb71c7d Add installation info for go language to README in polygerrit-ui
It is required to execute run-server.sh

Change-Id: I13e20df40de7f2a845d0c1a18c1fa3287fd94987
Signed-off-by: Eryk Szymanski <eryksz@gmail.com>
2016-03-18 16:06:48 +00:00
Han-Wen Nienhuys
b8fa0710c9 PolyGerrit: add --no-results-cache to the example commandline.
Change-Id: I85c5c1d2ad96651a9a46fe9483cd6bb07a007426
2016-03-15 19:08:24 +01:00
David Ostrovsky
9ac674d18b PolyGerrit: Mention style guide used in the project
Change-Id: I669f0ec7fd11bd2acf4b5ee27d0772c039ce6d6b
2016-02-13 10:45:34 +00:00
Dave Borowitz
3aeefe3341 Add quick script to run server.go
Build and extract bower_components to the local directory from
buck-out. This is easier than modifying server.go to serve from a zip
file.

Running `bower install` before server.go was the last remaining usage
of bower.json, so we can just remove it.

Change-Id: Ic4717a3a1652ad08e1cef871c0a207c2c382aa35
2015-12-03 13:49:40 -05:00
Dave Borowitz
c89f64cc7c Run PolyGerrit tests with Buck
Since Buck has no native support for web tests, wrap the tests in a
Python shim that calls wct. As in other Polymer cases, we need to
prepare a set of inputs and create a directory containing exactly what
wct expects to be there. Buck exposes resources to python_tests using
the pkg_resources API, which is cumbersome to use, and easier just to
ship around zip files as we do elsewhere.

Unlike other npm binaries we've encountered, the web-component-tester
module has numerous native dependencies, up to and including Selenium.
Rather than get in the game of distributing platform-specific
binaries, punt and require `wct` to be on the user's $PATH for now.

Tests are currently excluded in .buckconfig but can be run directly
with either:

  buck test //polygerrit-ui/app:polygerrit_tests
  buck test --include web

Change-Id: Ia314213925ac27ff271374a96ed539fb2acf0187
2015-11-25 11:14:05 -05:00
Dave Borowitz
41272759a6 PolyGerrit: Fix startup command in README.md
Change-Id: I89d7802c19522a0a6d172b1fdb6492b74ce8d3d3
2015-11-23 13:04:43 -05:00
Dave Borowitz
3232f85eda Update polygerrit-ui/README.md with some developer scenarios
Change-Id: I1716b9ed332bb2eab2db36cecb33db63c3320958
2015-11-23 08:57:58 -05:00
Andrew Bonventre
ba69835964 Add the skeleton of a new UI based on Polymer, PolyGerrit
This is the beginnings of an experimental new non-GWT web UI developed
using a modern JS web framework, http://www.polymer-project.org/. It
will coexist alongside the GWT UI until it is feature-complete.

The functionality of this change is light years from complete, with
a full laundry list of things that don't work. This change is simply
meant to get the starting work in and continue iteration afterward.

The contents of the polygerrit-ui directory started as the full tree of
https://github.com/andybons/polygerrit at 219f531, plus a few more
local changes since review started. In the future this directory will
be pruned, rearranged, and integrated with the Buck build.

Change-Id: Ifb6f5429e8031ee049225cdafa244ad1c21bf5b5
2015-11-09 22:01:28 +00:00