This repository was archived by the owner on Jul 8, 2020. It is now read-only.
forked from googleapis/google-cloud-node
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmessage-builder.js
More file actions
61 lines (56 loc) · 2.46 KB
/
Copy pathmessage-builder.js
File metadata and controls
61 lines (56 loc) · 2.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
/**
* Copyright 2016 Google Inc. All Rights Reserved.
*
* 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.
*/
'use strict';
var ErrorMessage = require('../classes/error-message.js');
/**
* The handler setup function serves to produce a bound instance of the
* of a factory for ErrorMessage class instances with configuration-supplied
* service contexts automatically set.
* @function handlerSetup
* @param {NormalizedConfigurationVariables} config - the environmental
* configuration
* @returns {ErrorMessage} - a new ErrorMessage instance
*/
function handlerSetup(config) {
/**
* The interface for creating new instances of the ErrorMessage class which
* can be used to send custom payloads to the Error reporting service.
* @returns {ErrorMessage} - returns a new instance of the ErrorMessage class
*/
function newMessage() {
// The API expects a reported error to contain a stack trace.
// However, users do not need to provide a stack trace for stack
// traces built using the message builder. Instead, here we store
// the stack trace with the parts that reference the error-reporting's
// internals removed. Then when the error is reported, the stored
// stack trace will be appended to the user's message for the error.
//
// Note: The stack trace at the point where the user constructed the
// error is used instead of the stack trace where the error is
// reported to be consistent with the behavior of reporting a
// an error when reporting an actual Node.js Error object.
var fauxError = new Error('');
var fullStack = fauxError.stack.split('\n');
var cleanedStack = fullStack.slice(2).join('\n');
var em = new ErrorMessage().setServiceContext(
config.getServiceContext().service,
config.getServiceContext().version);
em._autoGeneratedStackTrace = cleanedStack;
return em;
}
return newMessage;
}
module.exports = handlerSetup;