When user encounter error in dashboard, can we show the specific error information rather than 'Unexpected error'?

For example for Missing dataset error, can we show the error title to bubble up as 'Missing dataset' rather than 'Unexpected error'? It will be easier for user to see specific error right away.

<img width="674" alt="Screen Shot 2021-10-01 at 10 48 24 AM" src="https://user-image

Problem

See #3856 . Developer would like the ability to configure whether the developer menu or viewer menu is displayed while they are developing on cloud IDEs like Gitpod or Github Codespaces

Solution

Create a config option

showDeveloperMenu: true | false | auto

where

• true: always shows the developer menu locally and while deployed
• false: always sho

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

Problem

I've noticed that matplotlib currently doesn't support saving images in webp format, which I later confirmed by looking into supported file formats in backend_bases.py file.

Saving images in webp would definitely be useful for users who want to upload the graphs they generate in matplotlib to t

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

I haven't checked whether other options are missing.

Bugs and Questions

The Problem

While I was debugging another issue, I noticed that the example included two bars with the same x and y values, and when you mouse over one of these bars both tooltips show up. It seems like Victory uses the x/y value to determine whether the tooltip is active when there is not another identifier.

Reproduction

https://codesandbox.io/s/frosty-du

We could improve the Error: output to a user shown in the expression preview to tell them what the Type() is for a parameter being passed that is not compatible with the parameter type being expected.

Proposed solution

On our various HTML/XML GREL functions (htmlText(), wholeText(), ownText(), etc.) add the new Type().call(bindings, args) to the EvalError and rephrase the error text as n

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

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.