-
Notifications
You must be signed in to change notification settings - Fork 21
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
Closes #338, #228: Improvements to x-axis formatting #365
Conversation
(incorporates: show data source type when no doc link present (re #46))
Still can not use unpublished queries on dashboards.
addresses issue Madalin found that allows a click off the dialog box to close it without resetting the textbox
but don’t name a table abcdefghijklmnop.
I tried to make `JSON.stringify(this.visualization.options.columnMapping)` a variable to avoid repeating it, but if I make it a `let` the linter throws an error and if I make it a `const` then it doesn’t change with the UI and the logic doesn’t work. :( updated based on PR comments
Makes the _v of the schema browser toggle into a configurable string per data source. It is not required and if it is not filled in the toggle will not appear in the schema browser.
6fe90ee
to
2cda756
Compare
r+ @emtwo Would you mind opening a PR upstream with this? |
@jezdez thanks. Do we want to merge this here and also open the PR upstream? Or just open it upstream and wait for it merge there first? |
I've recently found out that Plotly has an option to auto detect the axis type:
https://plot.ly/javascript/reference/#layout-scene-xaxis-type Have you tried this instead? |
Thanks @arikfr! That seems to work and is a nicer and more concise alternative. Here are a couple of queries I used to test: For testing
For testing another (category) automatic x-axis type detection. Using
|
@@ -306,7 +306,7 @@ export default function init(ngModule) { | |||
sortX: true, | |||
legend: { enabled: true }, | |||
yAxis: [{ type: 'linear' }, { type: 'linear', opposite: true }], | |||
xAxis: { type: 'datetime', labels: { enabled: true } }, | |||
xAxis: { type: '-', labels: { enabled: true } }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to add this option to the xAxisScales
array (and probably change it to have labels for each one, because currently we use the value itself, which won't work for -
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay that makes sense, @emtwo could take another look at this?
👍 |
@emtwo Let's merge this here first and then open an upstream PR at the same time as well. I'm not sure how quick we can expect merging upstream into our master. |
Just to follow up on this, there is a PR upstream that is currently under review with some comments recently addressed: getredash#2542 I didn't want to merge this PR here if it was going to change during the review process upstream, so I've left it open. |
@emtwo The PR getredash#2542 has been merged upstream, is there work needed here to extend it in our fork with functionality that wasn't accepted? |
@jezdez My suggested portion of the patch here: 7fb937d to resolve #338 was not accepted because the solution would do a regex match on large numbers, not just dates. A couple of good suggestions are here: getredash#2542 (comment) Though, in my opinion, it may be best/easiest to just stick with the first suggestion there, which is what we're already doing or have the jobs that generate/process the data making it into Athena to convert I'm going to close this PR and #228 as it's being handled upstream. |
@emtwo Excellent, I fully agree. Thanks for your patience getting this upstreamed! |
No description provided.