Data visualization

^{Originally posted by sunker December 17, 2021}
When support for Metrics Insights was added to the GetMetricData api, a few new error codes were introduced. These should be handled as an error or possibly as a warning.

![Screenshot 2021-12-09 at 18 46 54](https://user-ima

Is your feature request related to a problem? Please describe.

Since SIP-9 in 2018, TypeScript has been a part of the Superset repo. Since SIP-36 in 2020 all new frontend code should be written in TypeScript. When modifying old functions/components, migrating to TypeScript is appreciated, but n

Summary

Aesthetically trivial, yet I've spotted a discrepancy with font sizes in our tooltip (front-end + back-end screenshots below).
I believe sections #1 and #2 should have the same font size?

![image](https://user-images.githubusercontent.com/27242399/139825179-4d62e3

In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

Bug summary

imshow extents cannot be expressed with units.

Code for reproduction

fig, ax = plt.subplots()
dates = np.arange("2020-01-01","2020-01-10 23:00", dtype='datetime64[h]')
ys = np.random.random(dates.size)
arr = np.random.random((10, 10))

ax.imshow(arr, extent=[dates[0], dates[1], 0, 10])

Actual outcome

Traceback (most recent call last):
  File "

Related issue: #2050

There are a lot of commented types in victory/src/index.d.ts and a TODO comment to add missing type definitions. I'm adding an issue for this so we can prioritize this work.

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

Proposal

Most applications typically have OK button in dialogs in a lower right corner. This has become nearly an industry norm in application designs.

OpenRefine should have a consistent design of button orders regarding Cancel / OK.

Needed Design Changes in frontend

• Change OpenRefine's dialogs to have a consistent design of button ordering regarding Cancel / OK.
• In dialogs

Hi!

My suggestion/request is simple. When filtering the data, sometimes one needs to use the edge values of the data distribution in the filter histogram.

For example, one wants to choose the data of an hourly distribution (from 0:00 to 24:00) for the time between 22:00 and 6:00 in the nighttime and discard the data from 6:00 till 22:00 during the daytime.

So, when filtering the data with

• Base README.md
• Quizzes
• Introduction base README
  • Defining Data Science README
  • Defining Data Science assignment
  • Ethics README
  • Ethics assignment
  • Defining Data README
  • Defining Data assignment
  • Stats and Probability README
  • Stats and Probability assignment
• Working with Data base README
  • Rel

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.