chore: Remove obsolete legacy visualizations#24675
Conversation
Codecov Report
@@ Coverage Diff @@
## master #24675 +/- ##
==========================================
- Coverage 68.97% 68.91% -0.07%
==========================================
Files 1902 1902
Lines 74007 73909 -98
Branches 8186 8186
==========================================
- Hits 51047 50931 -116
- Misses 20839 20857 +18
Partials 2121 2121
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
0888b3c to
612c971
Compare
There was a problem hiding this comment.
Switching out for a legacy chart which invokes the /superset/explore_json RESTful API endpoint.
a04d32e to
6b3902c
Compare
There was a problem hiding this comment.
Currently caching only works with legacy charts and removal of the TableViz now treats the Girls chart as a non-legacy chart. One could argue this is a regression—in terms of fewer charts being eligible for caching—but the problem will be rectified in #24671.
6b3902c to
eea28c3
Compare
There was a problem hiding this comment.
See previous comment.
There was a problem hiding this comment.
See previous comment.
There was a problem hiding this comment.
See previous comment.
There was a problem hiding this comment.
Any legacy viz type works.
There was a problem hiding this comment.
Any legacy viz type should work.
eea28c3 to
ac7761a
Compare
michael-s-molina
left a comment
There was a problem hiding this comment.
LGTM. Thanks for the cleanup.
|
Closing in favor of #24692. |
SUMMARY
Whilst working on #24671 I realize that some non-legacy charts (which are invoked via the
/api/v1/chartRESTful API endpoint) are still present insuperset.vizmeaning the logic outlined in said PR for differentiating between legacy and non-legacy charts was incorrect.This PR removes the following charts (which were marked as deprecated in 3.0 though in actuality were obsolete):
TableVizBigNumberVizBigNumberTotalVizwhich will ensure that the logic in #24671 will be correct.
Technically (as illustrated by the augmented tests) these visualization types could be invoked either using the legacy or non-legacy RESTful API endpoint, though in actuality (per the frontend logic) they would only ever be invoked under the later.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
I systematically went through all the visualization types in
superset/viz.py(all NVD3 and DeckGL charts were bucketed together) and inspected which RESTful API endpoint was being invoked, i.e., any chart using the RESTful/superset/explore_jsonendpoint (or similar) remained.ADDITIONAL INFORMATION