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.

Sign up for GitHub

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

fix(explore): Time comparison in Mixed Chart in GENERIC_CHART_AXES not working #22945

Merged
merged 3 commits into from
Feb 2, 2023
Merged

fix(explore): Time comparison in Mixed Chart in GENERIC_CHART_AXES not working #22945

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0d89cd6
fix(explore): Time comparison in MixedChart in GenericXAxes not working
kgabryje Feb 1, 2023
087fcfc
Add tests
kgabryje Feb 1, 2023
56e6eee
Override query columns with formData groupby
kgabryje Feb 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
fix(explore): Time comparison in MixedChart in GenericXAxes not working
  • Loading branch information
@kgabryje
kgabryje committed Feb 1, 2023
commit 0d89cd683086fe99c5b8ea851d28d2e67b32db11
7 changes: 2 additions & 5 deletions superset-frontend/plugins/plugin-chart-echarts/src/MixedTimeseries/buildQuery.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,11 +67,8 @@ export default function buildQuery(formData: QueryFormData) {
fd,
queryObject,
)
? timeComparePivotOperator(fd, queryObject)
: pivotOperator(fd, {
...queryObject,
columns: fd.groupby,
});
? timeComparePivotOperator(fd, baseQueryObject)
: pivotOperator(fd, baseQueryObject);
Copy link
Member

Choose a reason for hiding this comment

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

The problem with using baseQueryObject is that it's the query builder's best guess as to what a single query query context would look like. In other words it will apply the same value to both queries, despite the fact that they should be separate. For this reason, we need to stick to whatever we have in queryObject, as that should already be rendered with the correct options. For this reason I'd actually propose the following change, which seems to work in all my quick test cases (only time compare on query A, only time compare on query B, and time compare on both queries):

Suggested change
? timeComparePivotOperator(fd, baseQueryObject)
: pivotOperator(fd, baseQueryObject);
? timeComparePivotOperator(fd, {
...queryObject,
columns: fd.groupby,
})
: pivotOperator(fd, {
...queryObject,
columns: fd.groupby,
});

image

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the suggestion, done


const tmpQueryObject = {
...queryObject,
Expand Down