Gr-reporting is singleton and each element that needs to report can get its instance. A class implementation is cleaner and it's not creating unnecessary dom elements. Added mock of gr reporting enables easier way to test functions with gr reporting and it is also checking basic types of parameters. Change-Id: I039fce6dbcfd4956ff2c29805b3be7955b5f40ac
33 lines
1.1 KiB
JavaScript
33 lines
1.1 KiB
JavaScript
/**
|
|
* @license
|
|
* Copyright (C) 2020 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.
|
|
*/
|
|
import {initAppContext} from '../services/app-context-init.js';
|
|
import {initVisibilityReporter, initPerformanceReporter, initErrorReporter} from '../services/gr-reporting/gr-reporting.js';
|
|
import {appContext} from '../services/app-context.js';
|
|
|
|
if (!window.Polymer) {
|
|
window.Polymer = {
|
|
passiveTouchGestures: true,
|
|
lazyRegister: true,
|
|
};
|
|
}
|
|
window.Gerrit = window.Gerrit || {};
|
|
|
|
initAppContext();
|
|
initVisibilityReporter(appContext);
|
|
initPerformanceReporter(appContext);
|
|
initErrorReporter(appContext);
|