What happened:

1. user is on a viewPanel page
2. user clicks on top-nav "share" icon, expecting it to share the panel view
3. the generated link is for the dashboard, not the panel

What you expected to happen:
Maybe very experienced Grafana users will know that 1) the top-nav share link is always for the dashboard, even if you're on a panel view; and 2) panels have their own sha

Hello,
I want to show euros values on dashboard. But only the $ format are enable. When i changed the $ symbol to € i obtained an error.
How can I show euros value in a chart ?

I want something like "y_axis_format": "$,.2f" ==> to "y_axis_format": ",.2f€"

Regards,
Zied Sellami

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

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

Checklist

• This is not a victory-native specific issue. (Issues that only appear in victory-native should be opened here)

• I have read through the FAQ and Guides before asking a qu

The options "Include Schema" and "Include Contents" in the SQL exporter dialog can be a bit mysterious for users.

Proposed solution

Just like concrete SQL commands are included in the UI text elsewhere in the dialog ("DROP"), we could expand these phrases to mention the corresponding SQL commands ("CREATE TABLE", "INSERT").

Alternatives considered

We could also drop the mention

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

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