Elementary Community

Hi, I'm looking into to explicitly define package overrides for builtin materializations ~and it looks for me that materialization overrides are gone in the new 0.16.0 release. Does this mean I don't need to do anything?~. I found that the `test` materialization is override. Is a sulution to just implement the same materialization in my own project? Example in :thread:

```{% materialization test, default %}
  {% set result = elementary.materialize_test(dbt.materialization_test_default) %}
  {% do return(result) %}
{% endmaterialization %}

{% materialization test, adapter="snowflake" %}
  {%- if dbt.materialization_test_snowflake -%}
    {% set materialization_macro = dbt.materialization_test_snowflake %}
  {%- else -%}
    {% set materialization_macro = dbt.materialization_test_default %}
  {%- endif -%}
  {% set result = elementary.materialize_test(materialization_macro) %}
  {% do return(result) %}
{% endmaterialization %}```
ref: <https://github.com/elementary-data/dbt-data-reliability/blob/77477a01edc8607108ed7e8d72f86c1aca6ff640/macros/edr/materializations/test/test.sql#L1-L14|https://github.com/elementary-data/dbt-data-reliability/blob/77477a01edc8607108ed7e8d72f86c1aca6ff640/macros/edr/materializations/test/test.sql#[…]4>