Update check from new value instead of merging into old object

* Updating checks by merging the new object into the old creates
a bug where a property that's deleted in the new object, is still
preserved in the new object.
Fix this issue by updating checks by assigning the new value directly.

Change-Id: I7ed84eb84e287d88980098c9181f4316912c3c2f
2 files changed
tree: 3033e80e1ab77fd217af528457e49dd78619c69e
  1. gr-checks/
  2. java/
  3. javatests/
  4. proto/
  5. resources/
  6. test/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package.json
  14. README.md
README.md

Gerrit Code Review Checks Plugin

This plugin provides a unified experience for checkers (CI systems, static analyzers, etc.) to integrate with Gerrit Code Review.

This plugin uses polymer-cli to test.

After bower install, running polymer test -l chrome will run all tests in Chrome, and running polymer serve and navigating to http://127.0.0.1:8081/components/checks/gr-checks/gr-checks-view_test.html allows for manual debugging.

When upgrading the plugin, please use init:

java -jar gerrit.war init -d site_path

More details about “init” in https://gerrit-review.googlesource.com/Documentation/pgm-init.html