Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'tickFormat' property should affect only Axis for which it be declared #185

Closed
2 tasks done
alexwizp opened this issue Apr 23, 2019 · 3 comments · Fixed by #348
Closed
2 tasks done

'tickFormat' property should affect only Axis for which it be declared #185

alexwizp opened this issue Apr 23, 2019 · 3 comments · Fixed by #348
Assignees
Labels
enhancement New feature or request :legend Legend related issue released Issue released publicly

Comments

@alexwizp
Copy link
Contributor

alexwizp commented Apr 23, 2019

Version (please complete the following information):
3.11.2

Describe the bug
'tickFormat' property should affect only Axis for which it be declared

To Reproduce

Steps to reproduce the behavior:

  1. Create Chart with two Y-axis values
  2. Set 'tickFormat' format for first Axis e.g {{value}}F
  3. See result

Expected behavior
I expect to see '1F' for first axis and 1 for second

Screenshots
image

Checklist

  • every related Kibana issue is listed under Kibana Cross Issues list
  • kibana cross issue tag is associated to the issue if any kibana cross issue is present
@alexwizp alexwizp added bug Something isn't working :legend Legend related issue labels Apr 23, 2019
@markov00 markov00 changed the title [Legend List] 'tickFormat' property should affect only Axis for which it be declared 'tickFormat' property should affect only Axis for which it be declared Apr 23, 2019
@markov00
Copy link
Member

markov00 commented Jul 5, 2019

@alexwizp for this case let me summarize the possibility:

  1. if you want to visualize multiple series of the same data type, bytes, the same currency etc, you can just add a single Axis with a single tickFormat.

  2. if you want to add multiple series from different data types, like you want to add one series with currency and another with bytes, you should specify 2 Axis components. You should also specify two different groupIds one for the bytes and one for the currency, because you are displaying two different values on two different domains (bytes and currency).

2.5) if you want to have the same scale, for any specific reason, actually you can manually compute the min and max domain of the two series and apply the same domain to each series. You can then hide one or the other axis to have only one axis displayed.
Basically it works in the same way works for #169 (comment)

@markov00
Copy link
Member

markov00 commented Jul 5, 2019

We can add a basic formatter for each individual series, that will override, on the tooltip and on the legend the formatter of the axis if you think it's necessary.

@markov00 markov00 added enhancement New feature or request and removed bug Something isn't working labels Jul 5, 2019
markov00 added a commit that referenced this issue Aug 26, 2019
This commit add a new property for the series: useDefaultGroupDomain that allows to split series by groupId but keeps and compute the new groupId domain merging it with the global one

fix #169, fix #185
markov00 pushed a commit that referenced this issue Aug 26, 2019
# [10.3.0](v10.2.0...v10.3.0) (2019-08-26)

### Features

* compute global y domain on multiple groups ([#348](#348)) ([5ab46ca](5ab46ca)), closes [#169](#169) [#185](#185)
@markov00
Copy link
Member

🎉 This issue has been resolved in version 10.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@markov00 markov00 added the released Issue released publicly label Aug 26, 2019
AMoo-Miki pushed a commit to AMoo-Miki/OpenSearch-Dashboards that referenced this issue Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request :legend Legend related issue released Issue released publicly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants