@microsoft/applicationinsights-core-js 2.7.2-nightly.2111-08 → 2.7.2-nightly.2111-09

package/api-extractor.json

@@ -0,0 +1,361 @@
+/**
+ * Config file for API Extractor.  For more info, please visit: https://api-extractor.com
+ */
+ {
+    "$schema": "https://developer.microsoft.com/json-schemas/api-extractor/v7/api-extractor.schema.json",
+  
+    /**
+     * Optionally specifies another JSON config file that this file extends from.  This provides a way for
+     * standard settings to be shared across multiple projects.
+     *
+     * If the path starts with "./" or "../", the path is resolved relative to the folder of the file that contains
+     * the "extends" field.  Otherwise, the first path segment is interpreted as an NPM package name, and will be
+     * resolved using NodeJS require().
+     *
+     * SUPPORTED TOKENS: none
+     * DEFAULT VALUE: ""
+     */
+    // "extends": "./shared/api-extractor-base.json"
+    // "extends": "my-package/include/api-extractor-base.json"
+  
+    /**
+     * Determines the "<projectFolder>" token that can be used with other config file settings.  The project folder
+     * typically contains the tsconfig.json and package.json config files, but the path is user-defined.
+     *
+     * The path is resolved relative to the folder of the config file that contains the setting.
+     *
+     * The default value for "projectFolder" is the token "<lookup>", which means the folder is determined by traversing
+     * parent folders, starting from the folder containing api-extractor.json, and stopping at the first folder
+     * that contains a tsconfig.json file.  If a tsconfig.json file cannot be found in this way, then an error
+     * will be reported.
+     *
+     * SUPPORTED TOKENS: <lookup>
+     * DEFAULT VALUE: "<lookup>"
+     */
+    "projectFolder": ".",
+  
+    /**
+     * (REQUIRED) Specifies the .d.ts file to be used as the starting point for analysis.  API Extractor
+     * analyzes the symbols exported by this module.
+     *
+     * The file extension must be ".d.ts" and not ".ts".
+     *
+     * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+     * prepend a folder token such as "<projectFolder>".
+     *
+     * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+     */
+    "mainEntryPointFilePath": "<projectFolder>/types/applicationinsights-core-js.d.ts",
+  
+    /**
+     * A list of NPM package names whose exports should be treated as part of this package.
+     *
+     * For example, suppose that Webpack is used to generate a distributed bundle for the project "library1",
+     * and another NPM package "library2" is embedded in this bundle.  Some types from library2 may become part
+     * of the exported API for library1, but by default API Extractor would generate a .d.ts rollup that explicitly
+     * imports library2.  To avoid this, we can specify:
+     *
+     *   "bundledPackages": [ "library2" ],
+     *
+     * This would direct API Extractor to embed those types directly in the .d.ts rollup, as if they had been
+     * local files for library1.
+     */
+    "bundledPackages": [
+    ],
+  
+    /**
+     * Determines how the TypeScript compiler engine will be invoked by API Extractor.
+     */
+    "compiler": {
+      /**
+       * Specifies the path to the tsconfig.json file to be used by API Extractor when analyzing the project.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * Note: This setting will be ignored if "overrideTsconfig" is used.
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<projectFolder>/tsconfig.json"
+       */
+      // "tsconfigFilePath": "<projectFolder>/tsconfig.json",
+  
+      /**
+       * Provides a compiler configuration that will be used instead of reading the tsconfig.json file from disk.
+       * The object must conform to the TypeScript tsconfig schema:
+       *
+       * http://json.schemastore.org/tsconfig
+       *
+       * If omitted, then the tsconfig.json file will be read from the "projectFolder".
+       *
+       * DEFAULT VALUE: no overrideTsconfig section
+       */
+      // "overrideTsconfig": {
+      //   . . .
+      // }
+  
+      /**
+       * This option causes the compiler to be invoked with the --skipLibCheck option. This option is not recommended
+       * and may cause API Extractor to produce incomplete or incorrect declarations, but it may be required when
+       * dependencies contain declarations that are incompatible with the TypeScript engine that API Extractor uses
+       * for its analysis.  Where possible, the underlying issue should be fixed rather than relying on skipLibCheck.
+       *
+       * DEFAULT VALUE: false
+       */
+      // "skipLibCheck": true,
+    },
+  
+    /**
+     * Configures how the API report file (*.api.md) will be generated.
+     */
+    "apiReport": {
+      /**
+       * (REQUIRED) Whether to generate an API report.
+       */
+      "enabled": true,
+  
+      /**
+       * The filename for the API report files.  It will be combined with "reportFolder" or "reportTempFolder" to produce
+       * a full file path.
+       *
+       * The file extension should be ".api.md", and the string should not contain a path separator such as "\" or "/".
+       *
+       * SUPPORTED TOKENS: <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<unscopedPackageName>.api.md"
+       */
+      "reportFileName": "<unscopedPackageName>.api.md",
+  
+      /**
+       * Specifies the folder where the API report file is written.  The file name portion is determined by
+       * the "reportFileName" setting.
+       *
+       * The API report file is normally tracked by Git.  Changes to it can be used to trigger a branch policy,
+       * e.g. for an API review.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<projectFolder>/etc/"
+       */
+      "reportFolder": "<projectFolder>/dist/",
+  
+      /**
+       * Specifies the folder where the temporary report file is written.  The file name portion is determined by
+       * the "reportFileName" setting.
+       *
+       * After the temporary file is written to disk, it is compared with the file in the "reportFolder".
+       * If they are different, a production build will fail.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<projectFolder>/temp/"
+       */
+      // "reportTempFolder": "<projectFolder>/temp/"
+    },
+  
+    /**
+     * Configures how the doc model file (*.api.json) will be generated.
+     */
+    "docModel": {
+      /**
+       * (REQUIRED) Whether to generate a doc model file.
+       */
+      "enabled": true,
+  
+      /**
+       * The output path for the doc model file.  The file extension should be ".api.json".
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<projectFolder>/temp/<unscopedPackageName>.api.json"
+       */
+      "apiJsonFilePath": "<projectFolder>/dist/<unscopedPackageName>.api.json"
+    },
+  
+    /**
+     * Configures how the .d.ts rollup file will be generated.
+     */
+    "dtsRollup": {
+      /**
+       * (REQUIRED) Whether to generate the .d.ts rollup file.
+       */
+      "enabled": true,
+  
+      /**
+       * Specifies the output path for a .d.ts rollup file to be generated without any trimming.
+       * This file will include all declarations that are exported by the main entry point.
+       *
+       * If the path is an empty string, then this file will not be written.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<projectFolder>/dist/<unscopedPackageName>.d.ts"
+       */
+      "untrimmedFilePath": "<projectFolder>/dist/<unscopedPackageName>.d.ts",
+  
+      /**
+       * Specifies the output path for a .d.ts rollup file to be generated with trimming for a "beta" release.
+       * This file will include only declarations that are marked as "@public" or "@beta".
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: ""
+       */
+      // "betaTrimmedFilePath": "<projectFolder>/dist/<unscopedPackageName>-beta.d.ts",
+  
+  
+      /**
+       * Specifies the output path for a .d.ts rollup file to be generated with trimming for a "public" release.
+       * This file will include only declarations that are marked as "@public".
+       *
+       * If the path is an empty string, then this file will not be written.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: ""
+       */
+      // "publicTrimmedFilePath": "<projectFolder>/dist/<unscopedPackageName>-public.d.ts",
+  
+      /**
+       * When a declaration is trimmed, by default it will be replaced by a code comment such as
+       * "Excluded from this release type: exampleMember".  Set "omitTrimmingComments" to true to remove the
+       * declaration completely.
+       *
+       * DEFAULT VALUE: false
+       */
+      // "omitTrimmingComments": true
+    },
+  
+    /**
+     * Configures how the tsdoc-metadata.json file will be generated.
+     */
+    "tsdocMetadata": {
+      /**
+       * Whether to generate the tsdoc-metadata.json file.
+       *
+       * DEFAULT VALUE: true
+       */
+      // "enabled": true,
+  
+      /**
+       * Specifies where the TSDoc metadata file should be written.
+       *
+       * The path is resolved relative to the folder of the config file that contains the setting; to change this,
+       * prepend a folder token such as "<projectFolder>".
+       *
+       * The default value is "<lookup>", which causes the path to be automatically inferred from the "tsdocMetadata",
+       * "typings" or "main" fields of the project's package.json.  If none of these fields are set, the lookup
+       * falls back to "tsdoc-metadata.json" in the package folder.
+       *
+       * SUPPORTED TOKENS: <projectFolder>, <packageName>, <unscopedPackageName>
+       * DEFAULT VALUE: "<lookup>"
+       */
+      // "tsdocMetadataFilePath": "<projectFolder>/dist/tsdoc-metadata.json"
+    },
+  
+    /**
+     * Configures how API Extractor reports error and warning messages produced during analysis.
+     *
+     * There are three sources of messages:  compiler messages, API Extractor messages, and TSDoc messages.
+     */
+    "messages": {
+      /**
+       * Configures handling of diagnostic messages reported by the TypeScript compiler engine while analyzing
+       * the input .d.ts files.
+       *
+       * TypeScript message identifiers start with "TS" followed by an integer.  For example: "TS2551"
+       *
+       * DEFAULT VALUE:  A single "default" entry with logLevel=warning.
+       */
+      "compilerMessageReporting": {
+        /**
+         * Configures the default routing for messages that don't match an explicit rule in this table.
+         */
+        "default": {
+          /**
+           * Specifies whether the message should be written to the the tool's output log.  Note that
+           * the "addToApiReportFile" property may supersede this option.
+           *
+           * Possible values: "error", "warning", "none"
+           *
+           * Errors cause the build to fail and return a nonzero exit code.  Warnings cause a production build fail
+           * and return a nonzero exit code.  For a non-production build (e.g. when "api-extractor run" includes
+           * the "--local" option), the warning is displayed but the build will not fail.
+           *
+           * DEFAULT VALUE: "warning"
+           */
+          "logLevel": "warning",
+  
+          /**
+           * When addToApiReportFile is true:  If API Extractor is configured to write an API report file (.api.md),
+           * then the message will be written inside that file; otherwise, the message is instead logged according to
+           * the "logLevel" option.
+           *
+           * DEFAULT VALUE: false
+           */
+          // "addToApiReportFile": false
+        },
+  
+        // "TS2551": {
+        //   "logLevel": "warning",
+        //   "addToApiReportFile": true
+        // },
+        //
+        // . . .
+      },
+  
+      /**
+       * Configures handling of messages reported by API Extractor during its analysis.
+       *
+       * API Extractor message identifiers start with "ae-".  For example: "ae-extra-release-tag"
+       *
+       * DEFAULT VALUE: See api-extractor-defaults.json for the complete table of extractorMessageReporting mappings
+       */
+      "extractorMessageReporting": {
+        "default": {
+          "logLevel": "warning",
+          // "addToApiReportFile": false
+        },
+  
+        "ae-missing-release-tag": {
+          "logLevel": "none"
+        },
+        //
+        // . . .
+      },
+  
+      /**
+       * Configures handling of messages reported by the TSDoc parser when analyzing code comments.
+       *
+       * TSDoc message identifiers start with "tsdoc-".  For example: "tsdoc-link-tag-unescaped-text"
+       *
+       * DEFAULT VALUE:  A single "default" entry with logLevel=warning.
+       */
+      "tsdocMessageReporting": {
+        "default": {
+          "logLevel": "warning",
+          // "addToApiReportFile": false
+        }
+  
+        // "tsdoc-link-tag-unescaped-text": {
+        //   "logLevel": "warning",
+        //   "addToApiReportFile": true
+        // },
+        //
+        // . . .
+      }
+    }
+  
+  }
+  

package/applicationinsights-core-js.build.error.log

@@ -0,0 +1,205 @@
+(node:1152) ExperimentalWarning: The fs.promises API is experimental
+
+dist-esm/applicationinsights-core-js.js → dist/applicationinsights-core-js.min.js...
+created dist/applicationinsights-core-js.min.js in 3.4s
+
+dist-esm/applicationinsights-core-js.js → dist/applicationinsights-core-js.js...
+created dist/applicationinsights-core-js.js in 724ms
+
+dist-esm/applicationinsights-core-js.js → browser/applicationinsights-core-js.min.js...
+created browser/applicationinsights-core-js.min.js in 2.8s
+
+dist-esm/applicationinsights-core-js.js → browser/applicationinsights-core-js.js...
+created browser/applicationinsights-core-js.js in 589ms
+Warning: The API report file was missing, so a new file was created. Please add this file to Git:
+D:\a\1\s\shared\AppInsightsCore\dist\applicationinsights-core-js.api.md
+Warning: types/JavaScriptSDK.Interfaces/IAppInsightsCore.d.ts:38:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IAppInsightsCore.d.ts:43:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IChannelControls.d.ts:20:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IChannelControls.d.ts:21:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:37:37 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:38:37 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:47:34 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:48:34 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:75:22 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:75:14 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:75:8 - (tsdoc-undefined-tag) The TSDoc tag "@type" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:76:8 - (tsdoc-undefined-tag) The TSDoc tag "@memberof" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:90:113 - (tsdoc-code-fence-opening-indent) The opening backtick for a code fence must appear at the start of the line
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:90:129 - (tsdoc-code-fence-opening-indent) The opening backtick for a code fence must appear at the start of the line
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:91:108 - (tsdoc-code-fence-opening-indent) The opening backtick for a code fence must appear at the start of the line
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:91:123 - (tsdoc-code-fence-opening-indent) The opening backtick for a code fence must appear at the start of the line
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:105:8 - (tsdoc-undefined-tag) The TSDoc tag "@description" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:107:21 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:107:14 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:107:8 - (tsdoc-undefined-tag) The TSDoc tag "@type" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:108:8 - (tsdoc-undefined-tag) The TSDoc tag "@memberof" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:113:8 - (tsdoc-undefined-tag) The TSDoc tag "@description" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:115:21 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:115:14 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:115:8 - (tsdoc-undefined-tag) The TSDoc tag "@type" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IConfiguration.d.ts:116:8 - (tsdoc-undefined-tag) The TSDoc tag "@memberof" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:30:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:31:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:36:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:43:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:52:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/IDiagnosticLogger.d.ts:53:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:5:4 - (tsdoc-undefined-tag) The TSDoc tag "@interface" is not defined in this configuration
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:10:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:15:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:16:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:22:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:23:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationListener.d.ts:29:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:11:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:16:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:21:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:26:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:27:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:33:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:34:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK.Interfaces/INotificationManager.d.ts:40:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IPerfManager.d.ts:12:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IPerfManager.d.ts:24:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IPerfManager.d.ts:31:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IProcessTelemetryContext.d.ts:31:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IProcessTelemetryContext.d.ts:32:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK.Interfaces/IProcessTelemetryContext.d.ts:33:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/AppInsightsCore.d.ts:17:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/AppInsightsCore.d.ts:22:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CookieMgr.d.ts:18:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CookieMgr.d.ts:19:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:7:21 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:8:20 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:9:20 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:9:12 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:9:4 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:14:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:15:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:87:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:88:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:88:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:88:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:93:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:94:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:94:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:94:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:111:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:112:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:112:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:112:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:117:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:118:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:118:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:118:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:123:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:124:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:124:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:124:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:136:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:137:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:145:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:146:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:154:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:155:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:163:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:164:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:175:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:182:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:189:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:190:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:191:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:192:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:198:25 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:199:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:200:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:200:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:200:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:232:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:267:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:268:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:269:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:276:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:277:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:278:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:284:25 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:285:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:286:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:286:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:286:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:292:25 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:293:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:294:24 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:294:16 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:294:8 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:305:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/CoreUtils.d.ts:306:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:26:11 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:32:11 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:41:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:42:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:47:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:52:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:61:24 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/DiagnosticLogger.d.ts:62:23 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/EnvUtils.d.ts:3:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/EnvUtils.d.ts:8:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:12:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:13:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:14:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:15:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:21:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:22:30 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:23:22 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:24:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:32:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:38:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:39:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:76:11 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:77:20 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:77:12 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:77:4 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:82:11 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:83:20 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:83:12 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:83:4 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:88:11 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:89:20 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:89:12 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:89:4 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:95:11 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:96:20 - (tsdoc-escape-right-brace) The "}" character should be escaped using a backslash to avoid confusion with a TSDoc inline tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:96:12 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@"
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:96:4 - (tsdoc-undefined-tag) The TSDoc tag "@return" is not defined in this configuration
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:108:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:109:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:117:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:118:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:126:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:127:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:135:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:136:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:147:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:154:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:155:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:156:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:157:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:202:79 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:203:61 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:207:4 - (tsdoc-undefined-tag) The TSDoc tag "@memberof" is not defined in this configuration
+Warning: types/JavaScriptSDK/HelperFuncs.d.ts:213:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:14:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:19:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:24:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:29:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:30:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:36:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:37:15 - (tsdoc-param-tag-with-invalid-type) The @param block should not include a JSDoc-style '{type}'
+Warning: types/JavaScriptSDK/NotificationManager.d.ts:43:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/PerfManager.d.ts:53:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/PerfManager.d.ts:60:8 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/RandomHelper.d.ts:4:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/TelemetryHelpers.d.ts:6:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/TelemetryHelpers.d.ts:7:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
+Warning: types/JavaScriptSDK/TelemetryHelpers.d.ts:8:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen