-
Notifications
You must be signed in to change notification settings - Fork 14.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
chore: revert bignumber.js patch for charts and reapply the original bignumber.js change to SQL editor in an opt-in fashion #7210
Conversation
Codecov Report
@@ Coverage Diff @@
## lyftga #7210 +/- ##
=========================================
- Coverage 64.5% 64.5% -0.01%
=========================================
Files 424 423 -1
Lines 20667 20651 -16
Branches 2268 2264 -4
=========================================
- Hits 13332 13321 -11
+ Misses 7212 7207 -5
Partials 123 123
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## lyftga #7210 +/- ##
=========================================
- Coverage 64.5% 64.5% -0.01%
=========================================
Files 424 423 -1
Lines 20667 20651 -16
Branches 2268 2264 -4
=========================================
- Hits 13332 13321 -11
+ Misses 7212 7207 -5
Partials 123 123
Continue to review full report at Codecov.
|
76dc6f6
to
5b73a9c
Compare
Revert "Fix rendering regression from the introduction of bignumber (apache#6937)"
…sion in `actions/sqlLab.js` where it is needed (aka opt into bignumber.js).
5b73a9c
to
1912b6c
Compare
… snake_cased properties for deck vizzes. This reverts commit e0feec9.
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.
I don't have as much context on the Deck.gl changes so probably good for someone else to review that. The big number + @superset-ui
changes lgtm tho 👍
I also have little context on this and this looks a bit scary. Quick reverts are cool, but long standing reverts are dangerous, I dug in and 95 PRs have been merged since #6937, some of these could have built upon assumptions on top of #6937 ... In general it may be easier (if possible) to push forward instead. But if you feel like this is necessary and that you've covered all the basis, then I'm ok moving forward. |
@mistercrunch planning on pushing ahead. We're going to do a bug bash in staging with this change. There has been a lot of rendering regressions in charts and dashboards since the introduction of My thought is addressing the root cause of the past regressions outweighs the possibility of regressing the recent 95 PRs. We'll hopefully uncover any regression to these recent PRs in our bug bash. |
+1 Go for it, though I agree with Max, we should test some of the things that were added in between. I've had 2 fixes for the time filter that were related to this, eg. |
SUMMARY
This PR does the following:
superset-ui-connection
actions/sqlLab.js
(/results
and/sql_json
endpoints) where it is needed and make sure the existing unit tests for this still pass.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
ADDITIONAL INFORMATION
REVIEWERS
@kristw @williaster @soboko
cc @betodealmeida @mistercrunch