This project is mirrored from https://github.com/metabase/metabase.
Pull mirroring updated .
- Jan 14, 2022
-
-
Alexander Lesnenko authored
This reverts commit 5fdeed90.
-
Noah Moss authored
-
- Jan 13, 2022
-
-
Nemanja Glumac authored
* Turn this into a ~~dataset~~ model * Model revision history copy updates * Datasets -> Models copy update * "Dataset management -> Model management" copy update * This is a ~~dataset~~ model now * Models in data picker copy changes * Models in search app copy changes * Update models copy in tests * Update frontend/src/metabase/lib/revisions/revisions.unit.spec.js Co-authored-by:
Maz Ameli <maz@metabase.com> * Update frontend/src/metabase/lib/revisions/revisions.js Co-authored-by:
Maz Ameli <maz@metabase.com> * Fix and update e2e tests Co-authored-by:
Maz Ameli <maz@metabase.com>
-
Gustavo Saiani authored
-
Alexander Lesnenko authored
* clean up old static charts * specs
-
Nemanja Glumac authored
* Extract models into a separate e2e group * Split models tests into smaller logical units * Keep `getCollectionItemRow` helper scoped to a single file * Keep `testDataPickerSearch` helper scoped to a single file * Update the name from `datasets` to `models`
-
Ariya Hidayat authored
-
Gustavo Saiani authored
-
Jeff Bruemmer authored
-
Alexander Polyankin authored
-
Luis Paolini authored
We have to build and publish EE, otherwise some features can't be tested
-
Alexander Lesnenko authored
* add waterfall static viz e2e specs * fix createQuestionAndAddToDashboard command * formatting
-
Alexander Polyankin authored
-
Cam Saul authored
-
dpsutton authored
* Don't update tables in a schema one by one Code had wanted to log each table which is admirable. But on bigquery there can be 15,000 tables and this will lock up calls to /api/database. On stats they are taking about 18s for me. Need to do once and let the db do the heavy lifting * Also where schema is nil * slightly better query
-
- Jan 12, 2022
-
-
Ariya Hidayat authored
When the text representation gets reformatted, the old caret position might not be sensible anymore. Hence, just push the caret to the end. * Add e2e test for caret position after blur and refocus Co-authored-by:
Gustavo Saiani <gustavo@poe.ma>
-
dpsutton authored
-
Chris Wu authored
* Add Pulse URL param to email settings * Undo frontend changes -- make config only allowable by env var * Make config enterprise only * Address feedback * Change namespace and token feature * newline * Rename var and add docs
-
Dalton authored
* Cache dashboard parameter values * move some logic to utils files * Fix e2e tests * add comment + const to clarify getParameterValuesSearchKey
-
frannietrempe authored
-
Jeff Evans authored
Add functions to describe-database namespace for performing inclusive/exclusive schema filtering Add tests for these functions in isolation Update `:bigquery-cloud-sdk` driver and QP code to remove the single `dataset-id` conn-param Changing :bigquery-cloud-sdk` driver to use dataset inclusion/exclusion filters instead Updating `add.cy.spec.js` Cypress test to account for new structure Add data upgrade (via `driver/normalize-db-details` implementation) to change `dataset-id` property to inclusion filter Add test to confirm data upgrade Adding server side expansion of `:schema-filters` type connection property
-
Noah Moss authored
-
Alexander Polyankin authored
-
Alexander Polyankin authored
-
- Jan 11, 2022
-
-
Cam Saul authored
* Misc code cleanup * PR feedback
-
Cam Saul authored
-
Alexander Kiselev authored
* pratt parser diagnostics * ported over tests from custom parser branch * updated error types to support pos/len for error markers * updated compiler error to removed unnecessary plural * updated resolver to use new error type and pass through node information * updated error text in custom column e2e test * updated diagnostics to use new resolver error class * update recursive-parser passes to pass through node information * roll back error text fix in e2e tests * deleted fuzzing tests (they will be moved into the metabase/expression repo) * this is weird, setting e2e error text back to "Expected expression" * rolled back expression editor changes in handleInputBlur and moved diagnoseExpression first to fix exponent rewrite issue * roll back changes to compileExpression * update import paths in expressions case class identities get messed up
-
Cam Saul authored
-
Cam Saul authored
* Debugging QP Improvements * Appease namespace linter * Backport additional debug QP changes from #19384 * Test fix
-
Alexander Lesnenko authored
* Fix creating a new collection from navbar * add specs
-
Nemanja Glumac authored
Repro #19494: Dashboard filter with default value sends the wrong parameters to all cards of the same questions
-
Nemanja Glumac authored
-
Luis Paolini authored
* Build and publish branches * fixup whitespace * Update docker.yml Co-authored-by:
Kyle Doherty <5248953+kdoh@users.noreply.github.com>
-
Kyle Doherty authored
* update nav copy to be clearer * update tests
-
Ariya Hidayat authored
-
dpsutton authored
* Exclude archived collections from tree view This is a bit more nuanced that it might first appear. The bug report is the permissions editor for collections is showing child collections which are archived. But the api sends back ALL collections, regardless of archival state. So the FE knows to omit top-level archived collections but not archived child collections. So we thought about just having the FE remove all archived ones, but best to remove it from the response. One worry is that we're not sure if any callers want archived collections in the tree view or not. So right now they are removed with a `?exclude-archived=true` query param, but if we can demonstrate that no callers of the tree api ever want archived items we can make this the behavior, rather than an optional behavior. To verify that the tree api is sending back all collections, you can check ```clj collection=> (collection/collections->tree {} [{:archived false :name "foo" :id 1 :location "/"} {:archived true :name "foo" :id 2 :location "/1/"} {:archived true :name "its archived" :location "/" :id 3}]) ;; we have always sent back archived collections, both top level and children ({:archived false, :name "foo", :id 1, :location "/", :children ({:archived true, :name "foo", :id 2, :location "/1/", :children ()})} {:archived true, :name "its archived", :location "/", :id 3, :children ()}) ``` * hide archived collections from the collections permissions page (#19616) * fix incorrect issue number Co-authored-by:
Alexander Lesnenko <alxnddr@users.noreply.github.com> Co-authored-by:
Aleksandr Lesnenko <alxnddr@gmail.com>
-
Noah Moss authored
-
Dalton authored
* Hide table popover based on a few conditions * fix TS id type inference * use util fn
-
Alexander Polyankin authored
-
Howon Lee authored
Pursuant to the nits from #18678 and #18676
-