* feat(big-number): add option to align time range
In Superset, when a timeseries query has no data at the beginning period
or end period of the filtered time range, there will not no data records
at those periods, hence the trendline in Big Number chart would not
render those periods. This often causes confusion and misinterpretaiton
in dashboards, especially for those with multiple trendline charts
aligned with each other. They could all be a very smooth line, but
actually showing very different time ranges.
This PR adds an option "alignTimeRange" to apply the filtered time
range on the xAxis. Date periods for empty data will be rendered, but
there will be no connected lines, dots, or tooltips for them.
It's possible to still show tooltips for those periods, but I decided
not to do that as: 1) it makes things much more complicated; 2) I don't
want to confuse zero or nulls with empty data.
* fix(big-number): disable alignRange by default
* refactor(big-number): migrate to Typescript
* fix(big-number): typescript build
* fix(big-number): change tooltip trigger; fix storybook
* fix(big-number): move @types to dependencies
* fix(big-number): move all files to ts
* build(big-number): add @types/d3-color as dependency
* refactor(big-number): remove renderTooltip as prop
* feat(big-number): add timeRangeUseFallback options and some refactor
* fix(big-number): update formatting functions
* fix(big-number): update copy for no data
* fix(big-number): address PR feedbacks
* feat(big-number): replace timeRangeUseFallback with bigNumberFallback
* fix: upgrade @types/react-bootstrap
* build(big-number): move react-bootstrap to dependencies
* refactor(big-number): more coherent types
* feat(big-number): use alert box for fallback values
* build(big-number): remove react-bootstrap
* build: upgrade nimbus and fix versions
Keep running into building errors locally, so upgrade nimbus and
fix all related packages to the working latest version.
* feat(big-number): adjust fallback warning alignment
* build: use a non-fixed version for @types/shortid
* build: revert package versions in main
* fix(legacy-table): avoid React DOM
`jquery.datatables` will manipulate DOMs, sometimes remove them. In case
of component being reloaded with updated props, React will not be able
to find those removed nodes, causing a `cannot removeChild` error.
Because of the the way to assign row keys, if table shape changes (add
or remove columns), React may also have difficulty match the cached
nodes via keys.
In general it's a bad idea to directly manipulate React rendered DOM
nodes, so we better just let `jquery.datatables` handle everything.
In the future, once we removed `jquery.datatables`, a pure React
component will not have such issues.
* fix(legacy-table): handle the case when percentMetrics is null
* fix(legacy-table): linting errors
* refactor: use nimbus build
* test(legacy-table): add React component tests
* test(legacy-table): more sophisticated cases
* fix: address PR #392 comments
* chore(legacy-table): clean up tests case setups
Not seeing the console.warn errors anymore. So cleaning it up.
Previously it was from `<SuperChart />` component, but since we have
updated the test case to not use <SuperChart>, we are good now.
* fix(legacy-table): misleading comment
