Remove _getChangeUrlAnd methods

This methods obscure the actual calls unnecessarily. As can be seen from
this change, making direct call to restApiHelper is almost the same
amount of code. Most of the implementation was just forwarding
parameters, which is not necessary, since we can construct the "input
object" right away.

Additionally replace send with fetch. Part of the
difference that existed in the past between send() (with parsed: false)
and fetchRawJSON() is that send() used to also check the status of the
response. That's why when we replace send() with fetch(), we set
reportServerError to true.

Moving to fetch removes semantics of send(), where it
sometimes returns parsed response and sometimes plain Response. As
evident from usage in corresponding tests, this used to lead to
confusion. Developers would expect parsed response, where in fact no
parsing is being done.

reportEndpointAsId is likely just a typo that existed previously in the
codebase. It's never read (only set), and the used in the same places
where reportEndpointAsIs makes sense. So we treat it as such.

Similarly reportUrlAsIs is likely a mistake due to this being a
parameter that is used by fetchRawJSON, but not by send(). It would
previously be dropped without being used, with this change we treat it
as reportEndpointAsIs.

The setChangeTopic and setChangeHashtags can return undefined (and could
return 'null' in the past). The return type annotation is wrong here.
There was an issue of undefined result not being processed correctly,
but that has been addressed in previous change

While converting _getDiffComments, i've noticed _getDiffCommentsFetchUrl
is unused. Likely it became unused from edits in the past. Removed.

Google-Bug-Id: b/297849592
Release-Notes: skip
Change-Id: I699a3bb79e3b1e44a70de6b770539708ff156fda
6 files changed
tree: 73d93504d406a2d142b4f443ddd31f55dbcc575c
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. .bazelignore
  20. .bazelproject
  21. .bazelrc
  22. .bazelversion
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .gitreview
  28. .pydevproject
  29. .zuul.yaml
  30. BUILD
  31. COPYING
  32. INSTALL
  33. Jenkinsfile
  34. MODULE.bazel
  35. package.json
  36. README.md
  37. SUBMITTING_PATCHES
  38. version.bzl
  39. web-dev-server.config.mjs
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.

Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

Gerrit is the work of hundreds of contributors. We appreciate your help!

Please read the contribution guidelines.

Note that we do not accept Pull Requests via the Github mirror.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

The instruction how to configure GerritForge/BinTray repositories is here

On Debian/Ubuntu run:

    apt-get update && apt-get install gerrit=<version>-<release>

NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.

On CentOS/RedHat run:

    yum clean all && yum install gerrit-<version>[-<release>]

On Fedora run:

    dnf clean all && dnf install gerrit-<version>[-<release>]

Use pre-built Gerrit images on Docker

Docker images of Gerrit are available on DockerHub

To run a CentOS 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.