Oliver Laslett

### Description ### What problem does this solve?

In `` (and other places) we have to explicitly react (with useEffect) to when the query results change, then derive the chart options `getChartConfigAndOptions` and then set them on the...

`package-lock.yml` changes in 1.10.0 are not backwards compatible

1

Not sure if intended but this change: https://github.com/dbt-labs/dbt-core/pull/11488 is not backwards compatible. If I compile my project with dbt `1.10.*` it will generate a `package-lock.yml` file with the `name` attribute....

feat: support `tags` + `meta` under `config`

8

I compiled dbt projects with different `dbt` versions. The table below summarises the results. The `yaml source key` is the location of the config in the yaml files. I've included...

feat: lightdash generate meta under config

5

- Throws an error for columns using `meta` - so customers need to be on 1.9 to use lightdash generate - Updates `lighdash generate` to generate and merge `meta` under...

fix: support YAML boolean filter string representations "false" and "\!false"

2

## Summary Fixes YAML boolean filter parsing to correctly handle string representations of boolean values (`"false"`, `"true"`, `"\!false"`) by implementing proper type conversion in the filter SQL rendering logic. **Before**:...

fix: prevent empty dashboards from downloading all charts

2

## Summary - Fixed empty dashboards downloading all charts instead of 0 charts - Fixed hardcoded error messages showing wrong content type - Fixed chart slug accumulation bug across API...

Disallow ${TABLE} and ${field} is `sql_on` field without specifying the table ${table.dimension}

3

### Description Currently we accept: ```yaml joins: - join: table sql_on: ${field} = ${table.field} ``` But it's very confusing as to whether `${field}` should be a field on the base...

There is handling for special keywords in this file: https://github.com/joshtemple/lkml/blob/9fc81c0fd5abb504a7b15643cbd056745e1e020c/lkml/keys.py#L15 Including `action` The problem is that if I have a filter on a dimension called `action` it doesn't correctly parse...