-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
fix(chart): legacyRegularTime and charts are being rendered, and solves issue #26181 #26439
base: master
Are you sure you want to change the base?
Conversation
@sivasathyaseeelan I think you've stumbled on a very critical bug here. I believe checking for #23865 fixed something similar. Ping @kgabryje , let's sync up on this asap, I'll ping you on Slack. @sivasathyaseeelan are you on Superset Slack? It might be easier to discuss this there.. |
FYI @michael-s-molina I think this may be important to get fixed in both the 3.0 and 3.1 RCs that are being voted on right now.. |
Hello @villebro, yeah I on superset slack! I think changing export const legacyRegularTime: ControlPanelSectionConfig = {
...baseTimeSection,
controlSetRows: [['granularity_sqla'], ['time_range']],
}; will solve this issue and it works fine in my local machine. Can I apply this piece of code to modify this PR? |
I'm not sure about this. The only difference between the
Considering that this problem already exists in 3.0.2 and that is affects mostly legacy plugins, I believe we could cherry-pick the fix in the next patch. |
I think this change will break things when |
@kgabryje and @michael-s-molina I understood, then i will go and replace |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #26439 +/- ##
=======================================
Coverage 69.16% 69.16%
=======================================
Files 1948 1948
Lines 76054 76054
Branches 8493 8493
=======================================
Hits 52601 52601
Misses 21273 21273
Partials 2180 2180
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@michael-s-molina @kgabryje I did some more checking, and I misremembered how the generic chart x-axis charts import handle the time section. Sorry for the noisy escalation - It seems the majority of legacy charts work fine with the new time filter (=that essentially replaces the old time section), and no longer need the dedicated time section. However, I noticed, that at least the t-test chart is also no longer functioning with generic chart axes turned on. To DRY this up, we may want to consider creating a shared control that always has the time section, but if it's only event flow and t-test at this point, then maybe it's not worth the effort. |
Noticed this one has slipped through the cracks for quite some time. I'm not sure how critical it is at this point, but if it were to move forward, it looks like it needs a rebase at the very least. @michael-s-molina and @villebro might know best about how (or if) we want to move this forward from here, but I'll put this in Draft mode until it's rebased at the very least. |
SUMMARY
This PR solves the issue mentioned in #26181. I have solved the logical error in
legacyRegularTime
and also made some changes insuperset-frontend/plugins/legacy-plugin-chart-calendar/src/controlPanel.ts
for better app structure.BEFORE
Screencast.from.10-01-24.12.21.36.AM.IST.webm
AFTER
Screencast.from.10-01-24.12.23.35.AM.IST.webm
TESTING INSTRUCTIONS
Kindly create any chart which renders
legacyRegularTime
(Eg: Event Flow chart which is mentioned in #26181) and now you can be able to see desired result.ADDITIONAL INFORMATION