This commit converts almost all Polymer elements from Polymer-function
based components to class-based components. There are few files which
should be converted manually after this commit.
Change-Id: I9e597e79053e0a6b5d5c0f1b54676d11b9d81db7
Legacy indent rules doesn't handle all cases. As a result there are
different indents in .js files. This commit update eslint rules and add
autofix for incorrect indents. It is expected that fix should be run
after converting to class-based elements.
Change-Id: I9d37a3d4319e2af71ddb93100a6791b8ddb7de79
This reverts commit 0f8964bb628674e3671bc34fda6ed775d5c94132.
Reason for revert: Still needs more places to have undefined checks.
Notably this breaks the diff screen.
Change-Id: Ifeecb2272144a688c96e63a942b221482d4eb69d
This reverts the commit 3e7f5fdd3fb29fef7312b2d5d49dd172a294237f
as undefined check added for all computed properties and
observers with more than one dependencies.
Change-Id: I8e88dfeccdfb5d7dd296a44cc9d86ca5f8c70ab9
Polymer 2 deprecates the 'fire' method for legacy elements.
So let's use gerrit's core fire method which is almost exactly the same.
Change-Id: I59aebd29a89d26d9cb39e63e9a41afa9756b942f
When legacy-data-mixin.html is imported this will tell you on the console which observers need fixing regarding this change of behavior:
https://polymer-library.polymer-project.org/2.0/docs/upgrade#update-observers
This change was created by running this command line:
find polygerrit-ui/app/ -type f | xargs sed -i '/^ is: / a\ _legacyUndefinedCheck: true,'
Once all observers are fixed, this change will be reverted. This is tracked in https://bugs.chromium.org/p/gerrit/issues/detail?id=10723
Change-Id: Icccdfaa52bf77dfb25e949b2aa2402110f6c2276
This allows users to specify a non-HEAD base commit
when creating a new change from the web UI.
Bug: Issue 8857
Change-Id: Ic585fafacc4bf21cd1d8bd129e889b42180b80a7
These tags are preserved by the Closure compiler and vulcanize in order
to serve the license notices embedded in the outputs. In a standalone
Gerrit server, these license are also covered in the LICENSES.txt served
with the documentation. When serving PG assets from a CDN, it's less
obvious what the corresponding LICENSES.txt file is, since the CDN is
not directly linked to a running Gerrit server. Safer to embed the
licenses in the assets themselves.
Change-Id: Id1add1451fad1baa7916882a6bda02c326ccc988
Allow to propagate private-by-defaut configuration value. It also avoids
unnecessary requests, when invoked from the change view, because the
project configuration was already retrieved and can be just re-used.
Bug: Issue 8601
Change-Id: I5cdb3f0e12c53bf656653b0821c94317ba7fbb2d
Re-use create-change-dialog to create follow-up change in change
screen. There are two enhancements to the create change dialog:
branch section can be hidden and base change can be passed in.
In addition the REST API is extended to accept base change id.
Feature: Issue 8213
Change-Id: Ib39f73e6b88513ed12bba42405b6320d33f16f87
This also includes backwards compatibility with the old /projects/ url.
This only renames it for the admin interface. It does not rename it for
changes or anything else.
Bug: Issue 7754
Change-Id: Ia31d3f26871556729fb3c5b5b28ceca12da1ec7c
Since change I6fea9f8d55c7a38ac293057681874e9b480341ed,
it has added support for per project private config instead of doing
it globally.
Change-Id: I72767ae5be0344d5275da1c41253f3284978c10a
* This adds a new page called Project Command accessed by navigating to
<url>/projects/<project>,commands
* This supports creating a change through the new dialog (though note
you can't edit any files, will have to switch to gwtui to do that)
* Supports creating the change as a private and wip or one or the other.
* Supports the Run GC button allowing you to run gc on projects.
Feature: Issue 5232
Change-Id: Ibd3507c0fdb84303c8a978e3ea87f251582b13e8
