This project is mirrored from https://github.com/metabase/metabase.
Pull mirroring updated .
- Dec 01, 2021
-
-
dpsutton authored
* Only annotate collection tree with unarchived information * Update docstring of api to include here and below info
-
Jeff Bruemmer authored
-
Alexander Lesnenko authored
-
- Nov 30, 2021
-
-
frannietrempe authored
-
Ariya Hidayat authored
-
Jeff Bruemmer authored
-
Jeff Evans authored
* Limit autocomplete results for tables and fields Add limit of 50 total fields or tables returned from the autocomplete_suggestions API, which can be a mixture of tables and/or fields Adding test that confirms results are limited properly
-
Alexander Lesnenko authored
* add funnel static viz * prettier * support funnel formatting options, change measureText signature * fix tests * fix types * unhardcode legend text style * decrease static funnel step font size, fix warnings * update specs
-
Alexander Lesnenko authored
-
- Nov 29, 2021
-
-
Ariya Hidayat authored
Field references in custom expression must be correctly resolved as dimensions, segments, or metrics. For instance, `[Rating] > 4 AND [Expensive]` means that [Rating] is a dimension and [Expensive] is a segment. Before this change, this process was carried out inside the parser. This led to various corner cases which were not handled well, e.g. `COALESCE(CASE([X], [Y]))` apparently resolved both [X] and [Y] as dimensions. This was incorrect, as [X] has to be a segment, since it's part of the conditional clause in CASE(). With this change, all field references are resolved as an additional pass. Thus, the resolver has the full visibility of the operand types for both unary and binary operators, as well as argument types of all functions, including variadic ones such as CONCAT, COALESCE, and CASE.
-
Ariya Hidayat authored
-
Ariya Hidayat authored
-
Alexander Polyankin authored
-
Alexander Polyankin authored
-
Noah Moss authored
-
Alexander Polyankin authored
-
Alexander Polyankin authored
-
- Nov 28, 2021
-
-
Howon Lee authored
BE for progress bar for static viz, sasha put in the FE bits a bit ago
-
- Nov 27, 2021
-
-
Alexander Lesnenko authored
* XYChart * support axes formatting, support negative values for bars and areas * calculate chart bounds based on axes presence, ticks sizes * Add legend * legend for single column, more examples * polish, unit tests * clean mess * fix XYChart renders bars with the same names, add demo for an edge case * goal line support prettier * legend folder rename
-
- Nov 26, 2021
-
-
Alexander Lesnenko authored
* show trend previous value in full-screen mode * remove unused variable
-
Anton Kulyk authored
* Add E2E test for native dataset view * Use simple mode for native datasets
-
Alexander Polyankin authored
-
Anton Kulyk authored
-
Anton Kulyk authored
-
- Nov 25, 2021
-
-
Alexander Polyankin authored
-
- Nov 24, 2021
-
-
Ariya Hidayat authored
-
frannietrempe authored
-
Alexander Lesnenko authored
* update prettier * run prettier
-
- Nov 23, 2021
-
-
Ngoc Khuat authored
-
Noah Moss authored
-
Jeff Evans authored
Update bigquery and googleanalytics drivers dependencies to newer versions, such that their transitive dependencies on google-api-client/google-http-client match the versions used in the new BigQuery driver
-
Cam Saul authored
* Add index on QueryExecution card_id + started_at * Migrations linter shouldn't disallow legacymigrations > 382 * Remove old test
-
Noah Moss authored
-
Cam Saul authored
New dashboard query endpoints and consolidate Dashboard API/Public/Embed parameter resolution code (#18994) * Code cleanup * Make the linters happy * Add pivot version of the new endpoints * implement usage of the new dashboard card query endpoint (#19012) * add new endpoints to services.js * replace CardApi.query with the new endpoint + pass dashboardId * add parameter id to parameter object found on query body * run dashchards using card query endpoint when they're new/unsaved on dashboard * Update endpoint references in e2e tests * Remove count check from e2e test We can make sure a double-mapped parameter filter shows results from both fields, but unfortunately with the new endpoint, the results don't seem to work anymore. I think that's OK? Maybe? * skip corrupted filters test the query endpoint now results in a 500 error caused by a schema mismatch * fix a few e2e intercepted request mismatches * unskip filter corruption test and remove the part that no longer works Co-authored-by:
Dalton <daltojohnso@users.noreply.github.com>
-
Noah Moss authored
-
Alexander Polyankin authored
-
Maz Ameli authored
-
Jeff Bruemmer authored
-
Alexander Polyankin authored
-
- Nov 22, 2021
-
-
Noah Moss authored
-