Skip to content
This repository has been archived by the owner on Oct 30, 2021. It is now read-only.

Upgrades Radar Vis to Kibana 6.2.2 #43

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

varunsharma27
Copy link

Upgrades Radar Vis to Kibana 6.2.2

@CLAassistant
Copy link

CLAassistant commented Mar 16, 2018

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@szydan szydan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @varundbest
Thank you for your contribution

package.json Outdated
@@ -14,28 +14,5 @@
"repository": {
"type": "git",
"url": "[email protected]:sirensolutions/kibi-radar-chart-plugin.git"
},
"scripts": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please leave the script and devDependencies section
They are used by siren team

name: 'radar',
title: 'Kibi Radar Chart',
description: 'A radar chart is a graphical method of displaying multivariate data ' +
'in the form of a two-dimensional chart of three or more ' +
'quantitative variables represented on axes starting from the same point.' +
' The relative position and angle of the axes is typically uninformative.',
icon: 'fa-empire',
category: VisType.CATEGORY.KIBI,
category: CATEGORY.KIBI,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use CATEGORY.SIREN

addLevelScale: 1,
addLabelScale: 0.9,
addLevelNumber: 5
radar: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why you introduced this wrapping object? Is this required by kibana6?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, apparently kibana 6 starts rendering its own legend after detecting these params.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the name of the property be anything else instead of radar?
I mean does it have to match the name property?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I just named it 'radar' as it's a radar vis. What name would you prefer?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Radar is fine. I just wanted to know if it has to match the name
Actually, if you could just do the test to double check would be nice.
Like renaming it temporarily to something else like "radar1" and check that it would still work

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, changed the variable to 'config' as it is somewhat descriptive.
It has come to my notice that you're not exactly using these configs:
fontSize
shareYAxis
addTooltip
isDonut
So i have removed them.

…igs, restored package.json, changed CATEGORY to SIREN.
@szydan
Copy link
Contributor

szydan commented Mar 16, 2018

@varundbest Nice Thanks all good now
I'll not merge it yet as we are currently on 5.6.8 with all other components
For anyone who would like to use it please build from this PR branch

@varunsharma27
Copy link
Author

Perhaps you can park it at a release/6.2.2 branch till then.

@colmose
Copy link
Contributor

colmose commented Oct 4, 2018

jenkins test it

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants