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.

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

Merged
merged 3 commits into from
Apr 3, 2019

Conversation

xtinec
Copy link
Contributor

@xtinec xtinec commented Apr 3, 2019

SUMMARY

This PR does the following:

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
  • Manually verified that bignumber.js related React runtime warnings in SQL editor (i.e. expecting a number but getting an object) disappeared
  • Sanity check in charts and dashboards
ADDITIONAL INFORMATION
[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration. Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API
[ ] Fixes bug
[x] Refactors code
[ ] Adds test(s)
REVIEWERS

@kristw @williaster @soboko
cc @betodealmeida @mistercrunch

@codecov-io
Copy link

Codecov Report

Merging #7210 into lyftga will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
superset/assets/src/chart/ChartRenderer.jsx 7.57% <ø> (+0.53%) ⬆️
superset/assets/src/SqlLab/actions/sqlLab.js 70.64% <100%> (+0.29%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 200efac...76dc6f6. Read the comment docs.

@codecov-io
Copy link

codecov-io commented Apr 3, 2019

Codecov Report

Merging #7210 into lyftga will decrease coverage by <.01%.
The diff coverage is 10.52%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
...erset/assets/src/visualizations/deckgl/factory.jsx 0% <ø> (ø) ⬆️
superset/assets/src/visualizations/deckgl/utils.js 94.33% <ø> (ø) ⬆️
superset/assets/src/chart/ChartRenderer.jsx 7.57% <ø> (+0.53%) ⬆️
...c/visualizations/deckgl/layers/Scatter/Scatter.jsx 0% <0%> (ø) ⬆️
...t/assets/src/visualizations/deckgl/Multi/Multi.jsx 0% <0%> (ø) ⬆️
...c/visualizations/deckgl/layers/Geojson/Geojson.jsx 0% <0%> (ø) ⬆️
...ets/src/visualizations/deckgl/layers/Grid/Grid.jsx 0% <0%> (ø) ⬆️
...ets/src/visualizations/deckgl/layers/Path/Path.jsx 0% <0%> (ø) ⬆️
...sualizations/deckgl/CategoricalDeckGLContainer.jsx 0% <0%> (ø) ⬆️
...c/visualizations/deckgl/layers/Polygon/Polygon.jsx 0% <0%> (ø) ⬆️
... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 200efac...6b185fb. Read the comment docs.

@xtinec xtinec force-pushed the xtinec--revert-big-number-js-usage branch from 76dc6f6 to 5b73a9c Compare April 3, 2019 02:54
xtinec added 2 commits April 2, 2019 22:06
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).
@xtinec xtinec force-pushed the xtinec--revert-big-number-js-usage branch from 5b73a9c to 1912b6c Compare April 3, 2019 05:06
… snake_cased properties for deck vizzes.

This reverts commit e0feec9.
@xtinec xtinec changed the title revert: bignumber patch to prevent rendering regression in charts chore: revert bignumber.js patch for charts and reapply the original bignumber.js change to SQL editor in an opt-in fashion Apr 3, 2019
@xtinec xtinec added #code-quality lyft Related to Lyft labels Apr 3, 2019
Copy link
Contributor

@williaster williaster left a 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 👍

@mistercrunch
Copy link
Member

mistercrunch commented Apr 3, 2019

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.

@xtinec
Copy link
Contributor Author

xtinec commented Apr 3, 2019

@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 bignumber.js usage in superset-ui-connection in Jan. These regressions are in the core areas of the entirety of Superset. We discussed with the airbnb folks and decided we should do this reversion.

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.

@betodealmeida
Copy link
Member

+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.

@xtinec xtinec merged commit 8e14807 into apache:lyftga Apr 3, 2019
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.34.0 labels Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels lyft Related to Lyft 🚢 0.34.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants