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

fix: null dates in table chart #17974

Merged
merged 1 commit into from
Jan 10, 2022

Conversation

etr2460
Copy link
Member

@etr2460 etr2460 commented Jan 8, 2022

SUMMARY

Currently, when a date is null and it's in a temporal column, it renders as 1970-01-01 instead of N/A. This PR fixes it

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Test dataset (generated in SQL Lab):
Screen Shot 2022-01-07 at 7 36 27 PM

Table chart before fix:
Screen Shot 2022-01-07 at 7 37 06 PM

Table chart after fix:
Screen Shot 2022-01-07 at 7 36 38 PM

TESTING INSTRUCTIONS

CI, new unit test, create a dataset with a temporal column in dev, add at least one row with null, ensure it renders as N/A

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

to: @ktmud @graceguo-supercat @michael-s-molina @rusackas

Copy link
Member

@rusackas rusackas left a comment

Choose a reason for hiding this comment

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

LGTM! Thank you!

@codecov
Copy link

codecov bot commented Jan 8, 2022

Codecov Report

Merging #17974 (8362156) into master (cb97e37) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #17974   +/-   ##
=======================================
  Coverage   67.08%   67.08%           
=======================================
  Files        1611     1611           
  Lines       64919    64920    +1     
  Branches     6871     6872    +1     
=======================================
+ Hits        43548    43551    +3     
+ Misses      19504    19503    -1     
+ Partials     1867     1866    -1     
Flag Coverage Δ
javascript 53.79% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...lugins/plugin-chart-table/src/utils/formatValue.ts 70.58% <100.00%> (+14.33%) ⬆️

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 cb97e37...8362156. Read the comment docs.

@geido
Copy link
Member

geido commented Jan 10, 2022

/testenv up

@github-actions
Copy link
Contributor

@geido Ephemeral environment spinning up at http://54.187.69.126:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

Copy link
Member

@geido geido left a comment

Choose a reason for hiding this comment

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

LGTM!

@etr2460 etr2460 merged commit 1e544ce into apache:master Jan 10, 2022
@github-actions
Copy link
Contributor

Ephemeral environment shutdown and build artifacts deleted.

shcoderAlex pushed a commit to casual-precision/superset that referenced this pull request Feb 7, 2022
bwang221 pushed a commit to casual-precision/superset that referenced this pull request Feb 10, 2022
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 1.5.0 labels Mar 13, 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 size/S v1.4.1 🚢 1.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants