splunk-events - npm Package Compare versions

Comparing version 1.4.0 to 1.4.1

CHANGELOG.md

		@@ -10,3 +10,7 @@ # Changelog

		## [1.4.0] - 2020-09-17
		## [1.4.1] - 2020-09-18
		### Fixed
		- Infinite loop in flush without custom request function.

		## [1.4.0] - 2020-09-17 [YANKED]
		### Changed
		@@ -13,0 +17,0 @@ - Migrate to TypeScript :tada:

lib/splunk-events.d.ts

		@@ -88,3 +88,3 @@ import { FetchContext } from './request';
		/**
		* Logs a event to Splunk.
		* Logs an event to Splunk.
		*
		@@ -105,7 +105,7 @@ * This method will send the data to the Splunk endpoint configured
		* regarding the workflow, use values such as "checkout-cart" for events
		* that happened in the Cart page of Checkout.
		* that happened in the Cart page of Checkout for example.
		* @argument eventData Any custom event data you may find useful to log
		* together that can provide more information in case of debugging.
		* together that can provide more information.
		* @argument account In multi-tenant environment it can be useful to know
		* the exact account this event is happnening in, to ease the debugging.
		* the exact account this event is happening in.
		*/
		@@ -112,0 +112,0 @@ logEvent: (level: string, type: string, workflowType: string, workflowInstance: string, eventData?: EventData \| null, account?: string) => void;

lib/splunk-events.js

		@@ -23,3 +23,3 @@ "use strict";
		/**
		* Logs a event to Splunk.
		* Logs an event to Splunk.
		*
		@@ -40,7 +40,7 @@ * This method will send the data to the Splunk endpoint configured
		* regarding the workflow, use values such as "checkout-cart" for events
		* that happened in the Cart page of Checkout.
		* that happened in the Cart page of Checkout for example.
		* @argument eventData Any custom event data you may find useful to log
		* together that can provide more information in case of debugging.
		* together that can provide more information.
		* @argument account In multi-tenant environment it can be useful to know
		* the exact account this event is happnening in, to ease the debugging.
		* the exact account this event is happening in.
		*/
		@@ -141,3 +141,3 @@ this.logEvent = function (level, type, workflowType, workflowInstance, eventData, account) {
		this.debouncedFlush = (_m = this.debouncedFlush) !== null && _m !== void 0 ? _m : debounce_1["default"](this.flush, this.debounceTime);
		this._requestImpl = (_p = (_o = config.request) !== null && _o !== void 0 ? _o : this.request) !== null && _p !== void 0 ? _p : request_1.fetchRequest;
		this._requestImpl = (_p = (_o = config.request) !== null && _o !== void 0 ? _o : this._requestImpl) !== null && _p !== void 0 ? _p : request_1.fetchRequest;
		this.injectTimestamp = (_q = config.injectTimestamp) !== null && _q !== void 0 ? _q : false;
		@@ -144,0 +144,0 @@ this.shouldParseEventData = (_r = config.shouldParseEventData) !== null && _r !== void 0 ? _r : true;

package.json

		{
		"name": "splunk-events",
		"version": "1.4.0",
		"version": "1.4.1",
		"description": "Javascript lib to create Splunk Logs via HTTP",
		@@ -5,0 +5,0 @@ "main": "lib/splunk-events.js",

New alerts