New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@splunk/visualization-encoding

Package Overview
Dependencies
Maintainers
15
Versions
79
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@splunk/visualization-encoding - npm Package Compare versions

Comparing version 20.2.0 to 20.3.0

formatters/Default.js

6

DataFrame.js

@@ -245,2 +245,5 @@ /*!

const dp1 = this.lastPoint();
if (dp1 === undefined) {
return undefined;
}
const field = dp1.field;

@@ -374,2 +377,5 @@ const { type, value: val1 } = dp1.getValue();

static fromJsonCols(columnarData) {
if (!columnarData) {
return new DataFrame([]);
}
// fixme todo why do we expect an object like {data:{fields, columns}}? Why don't we just expect something like {fields, columns}? The nesting inside 'data' feels useless

@@ -376,0 +382,0 @@ const { data: { fields: fields = [], columns: columns = [] }, } = columnarData;

@@ -245,2 +245,5 @@ /*!

const dp1 = this.lastPoint();
if (dp1 === undefined) {
return undefined;
}
const field = dp1.field;

@@ -374,2 +377,5 @@ const { type, value: val1 } = dp1.getValue();

static fromJsonCols(columnarData) {
if (!columnarData) {
return new DataFrame([]);
}
// fixme todo why do we expect an object like {data:{fields, columns}}? Why don't we just expect something like {fields, columns}? The nesting inside 'data' feels useless

@@ -376,0 +382,0 @@ const { data: { fields: fields = [], columns: columns = [] }, } = columnarData;

3

DataSeries.js

@@ -245,2 +245,5 @@ /*!

const dp1 = this.lastPoint();
if (dp1 === undefined) {
return undefined;
}
const field = dp1.field;

@@ -247,0 +250,0 @@ const { type, value: val1 } = dp1.getValue();

@@ -245,2 +245,5 @@ /*!

const dp1 = this.lastPoint();
if (dp1 === undefined) {
return undefined;
}
const field = dp1.field;

@@ -374,2 +377,5 @@ const { type, value: val1 } = dp1.getValue();

static fromJsonCols(columnarData) {
if (!columnarData) {
return new DataFrame([]);
}
// fixme todo why do we expect an object like {data:{fields, columns}}? Why don't we just expect something like {fields, columns}? The nesting inside 'data' feels useless

@@ -376,0 +382,0 @@ const { data: { fields: fields = [], columns: columns = [] }, } = columnarData;

8

package.json

@@ -5,3 +5,3 @@ {

"author": "Splunk",
"version": "20.2.0",
"version": "20.3.0",
"scripts": {

@@ -44,5 +44,5 @@ "build": "NODE_ENV=production webpack --config ./webpack.config.js --bail",

"@splunk/react-docs": "^0.7.0",
"@splunk/visualization-build-tools": "^20.2.0",
"@splunk/visualization-themes": "^20.2.0",
"@splunk/visualizations-shared": "^20.2.0",
"@splunk/visualization-build-tools": "^20.3.0",
"@splunk/visualization-themes": "^20.3.0",
"@splunk/visualizations-shared": "^20.3.0",
"@splunk/webpack-configs": "^4.0.0",

@@ -49,0 +49,0 @@ "@types/jest": "^25.1.4",

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc