Update gr-comment-api
Previously, nested components (that are never standalone) were making
their own requests for comments, creating unecessary duplicate API
requests.
Some requests were made to the rest API directly (for example,
gr-change-view requested comments this way), and some were through the
gr-comment-api, which also helped handle comment manipulation and
reorganization.
Instead of ad-hoc comment requesting, move all comment requests to the
top level (standalone) component, and use an object prototype to
generate _changeComments as a property on gr-comment-api. This is an
immutable object that can be passed to the inner components
(file list, etc), and includes the methods needed to manipulate
comments into the forms
necessary.
When a child component needs to trigger a refresh of the comments, fire
an event that the parent event handles (see gr-file-list l.867).
Bug: Issue 6953
Change-Id: Ic4b6cf16520baae65d8cf956c311a60f2a70a2e1
2017-11-02 16:07:13 -07:00
|
|
|
// Copyright (C) 2017 The Android Open Source Project
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
(function() {
|
|
|
|
'use strict';
|
|
|
|
|
|
|
|
Polymer({
|
|
|
|
is: 'comment-api-mock',
|
|
|
|
|
|
|
|
properties: {
|
|
|
|
_changeComments: Object,
|
|
|
|
},
|
|
|
|
|
|
|
|
loadComments() {
|
|
|
|
return this._reloadComments();
|
|
|
|
},
|
|
|
|
|
2017-11-08 12:02:04 -08:00
|
|
|
/**
|
|
|
|
* For the purposes of the mock, _reloadDrafts is not included because its
|
|
|
|
* response is the same type as reloadComments, just makes less API
|
|
|
|
* requests. Since this is for test purposes/mocked data anyway, keep this
|
|
|
|
* file simpler by just using _reloadComments here instead.
|
|
|
|
*/
|
|
|
|
_reloadDraftsWithCallback(e) {
|
Update gr-comment-api
Previously, nested components (that are never standalone) were making
their own requests for comments, creating unecessary duplicate API
requests.
Some requests were made to the rest API directly (for example,
gr-change-view requested comments this way), and some were through the
gr-comment-api, which also helped handle comment manipulation and
reorganization.
Instead of ad-hoc comment requesting, move all comment requests to the
top level (standalone) component, and use an object prototype to
generate _changeComments as a property on gr-comment-api. This is an
immutable object that can be passed to the inner components
(file list, etc), and includes the methods needed to manipulate
comments into the forms
necessary.
When a child component needs to trigger a refresh of the comments, fire
an event that the parent event handles (see gr-file-list l.867).
Bug: Issue 6953
Change-Id: Ic4b6cf16520baae65d8cf956c311a60f2a70a2e1
2017-11-02 16:07:13 -07:00
|
|
|
return this._reloadComments().then(() => {
|
|
|
|
return e.detail.resolve();
|
|
|
|
});
|
|
|
|
},
|
|
|
|
|
|
|
|
_reloadComments() {
|
|
|
|
return this.$.commentAPI.loadAll(this._changeNum)
|
|
|
|
.then(comments => {
|
|
|
|
this._changeComments = this.$.commentAPI._changeComments;
|
|
|
|
});
|
|
|
|
},
|
|
|
|
});
|
|
|
|
})();
|