* Update react related imports

* Update places with combined default and named type

* Autofix type imports

* Fix unused eslint-disable

* Include cljs_release to eslintignore

* Autofix type imports

* Add typescript rule

Added bug bot integration with Slack

Add test to dashboard parameter should occupy whole horizon space when navigating to dashboards inapp in interactive embed (#33337)

* Add a repro for #30645

* Reuse util function

* Extract logic to generate next unsaved card id to another function

This reverts commit a5776529.

* Add recursive capabilities to segment expansion

* Add test

* Add error type

* Update `nested-segments-test`

* Remove redundant `Database` and `Table`

* Convert use of `with-temp*` to `t2.with-temp`

In CLJS there's no distinction between nil and undefined, but JS there is
and goog.object/get does not check undefined.

* fix specific aria-label for generic sidebar

* hide dashboard subscription button

- when user is non-admin and email & slack are not configured

* forward non-admin user to configured subscription form

* fix: show pulse list after creation for non-admins

- when pulse count is 0 and a new pulse is added by non-admins, it used to auto-redirect to the creation form again b/c the new pulse was not loaded before the forwarding would occur again

* refactor magic strings

* fix error when pulses has no length attribute

* validate forwarding in subscriptions for non-admins

* add remaining specs

* updated tests for new subscriptions forwarding for non-admins

* update tests for subscriptions forwarding for non-admins

* update tests for subscriptions forwarding for non-admins

* fix unit tests

* update dashboard subscriptions button to exclude heading cards

* [WIP] convert E2E tests to unit tests

* convert subscriptions button test to unit test

* restore some E2E tests

* fix unit tests

- new fetch request occurring in child component DashboardHeader was causing these tests to fail on the fetch request because there was no fallback

* Use findByLabelText as we're targeting a checkbox input

* Add reproduction test for #22265

* Break second question after adding it to series

* Format code

* Correct the repro: Use valid question first before turning it invalid

* Speed up E2E test by preparing data using API

---------

Co-authored-by: Mahatthana Nomsawadi <mahatthana.n@gmail.com>

* Split `admin` E2E group and merge it with `auditing`

* Run new `admin-2` group in CI

* remove add new h2 db test

* update setup specs to test mysql and postgres connections

* check for mongodb connection string errors

* Pass dashboardId and dashcardId in QueryDownloadWidget in ViewFooter
* Add missing dashboardId and dashcardId in QueryDownloadWidget.tsx
* spec

---------

Co-authored-by: Robin <e.robin154@gmail.com>

We have to sets of functions that deal with the information about Metabase version.
1. During build process we create `version.properties` file
2. During release we create new `version-info.json` or `version-info-ee.json` files that we store in AWS

The first contains the information about the current Metabase version.
It's used to generate info in "About Metabase" window, among others.

Calling both namespaces `version-info` leads to unnecessary confusion.
This commit should make the disctinction between the two more obvious and clear.

* Add a repro for 16663

* Make test real

* Address review

* Update e2e/test/scenarios/dashboard-filters/reproductions/16663-filters-can-stay-in-url.cy.spec.js

Co-authored-by: Kamil Mielnik <kamil@kamilmielnik.com>

* typo

---------

Co-authored-by: Kamil Mielnik <kamil@kamilmielnik.com>

* Modify an E2E test and unskipped it

* Fix calling wrap when table is undefined

* troubleshooting CI

* Fix failed test on CI

* Adding is-true and is-false operators

* Adding unit tests

* All Operators adjustment

* PR Feedback

* add "is equal to" in spec

* adding e2e test

---------

Co-authored-by: Jesse Devaney <22608765+JesseSDevaney@users.noreply.github.com>

We're currently running way too many jobs on every single commit in CI.

Frontend code coverage is a good example.
We can safely move it to run only on the merge to master.

Experimental run showed that running FE unit tests without the coverage takes 22 minutes.
The run with the coverage takes ~33 minutes on the same machine.

Furthermore, we don't have to run Chromatic on every single run.
On merge to master should be more than enough.

* added issuer props to list of saml settings

* adding e2e test

* using unit test instead

* Convert `VisibilityToggler` to TypeScript

* Conver `RightClickPopover` to TypeScript

* Convert `DataReferenceButton` to TypeScript

* Convert `NativeVariablesButton` to TypeScript

* Convert `SnippetSidebarButton` to TypeScript

* Convert `NativeQueryEditorSidebar` to TypeScript

* Make `size` prop required for sidebar buttons

* Fix setting default prop value twice

* Address comments

* Remove `NativeVariablesButton.shouldRender`

* Add disabled prop to ListItem

* Disable syncing tables in data reference page

* Add disabled prop to Root

* Format code

* Add a test case for disabled ListItem

* Extract PLACEHOLDER_TEXT

* Fix typo

* Update test name

* Add test boilerplate

* Add a basic rendering test for TableList

* Add data-testid prop to ListItem

* Add tests for tables with various initial_sync_status

* Improve assertions

* Add style assertions

* Remove unused argument and inline defaultProps