analytics

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

There is a lack of global link styles, which is an accessibility issue.

(Old part of the issue)

Steps to reproduce:

1. Try to tab throu

Screenshot

Description

chart 3 dot menu is behind the chart title panel in chart maximize mode

Describe the bug
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best

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

Is your feature request related to a problem? Please describe.
There are parts of the website that can use improvements in increasing the accessibility of the website.

**Describe the solution you

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

Is your feature request related to a problem?

It takes too long for me to open the dashboard I'm checking out daily. I need to open posthog dashboards -> find the right one -> click. I'd like to get there fastest.

Describe the solution you'd like

Include dashboard name in page title. This way my URL bar and page history will suggest it when looking for the dashboard.

Describe

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo

In the past a conversion through Number "interface" has proven to be able to mask bugs in the code.
We should remove these conversions from io.trino.spi.type.TypeUtils#writeNativeValue.

Wrong example for python_artifact usage. Instead, it is showing the EventMetadata.float usage.
https://docs.dagster.io/_apidocs/solids#dagster.EventMetadata.python_artifact