commit 272a803f38a935feca410dc7683cf2d37f40f409
author Patrick Hiesel <hiesel@google.com> Tue May 30 16:48:48 2017 +0200
committer Patrick Hiesel <hiesel@google.com> Tue Jul 11 17:18:10 2017 +0200
tree 5ea64a6405de25408a8d4c9e6f449b0b281e51bd
parent b771e8d2e0dc976f7ecb8e5f8259d9789006ee24

Rewrite GWT UI to use project name in addition to numeric change ID

This change adapts the GWT UI to recognize a project name in the URL
alongside the numeric change ID and integrate it into all REST API calls
made on /changes.

This is an effort towards having the project in all REST API calls to
/changes which will make routing Gerrit requests easier. On top, it
doesn't require secondary index lookups for trivial calls like /detail.

In contrast to the original proposal, changes will be served at
/c/project-name/+/123 instead of /p/project-name/+c/1234.
This is to stay more consistent with the REST API which serves all
changes at /changes instead of /projects.
The only difference between the UI and the API is now that the UI uses
'/+/' as a delimiter while the API uses '~'. In addition project names
in the API need to be URL encoded. This enables us to use the new change
id that includes the project also in a later part of the URL.
In the UI, this isn't needed and at the same time we want to maximize
the readability of URLs which is done by the two differences noted
above.

If a user uses a URL without the project (/c/123), we retrieve the
project upon the first API call and rewrite the URL.

All instances of Project.NameKey and String project are marked
@Nullable where they can actually be null. In the API layer they are
consistently marked @Nullable to reflect the current status of the
backend. That is, a project can optionally be provided. This
might be changed to a more strict policy at a later stage.

Change-Id: Ie3feee2e3b3e3b91b8d646d0326b7ada6134a0f9