@kapa.ai In my project, I'm using custom aliases to rename elementary models (e.g.

elementary_test_results

->

dbt_poc__elementary__elementary_test_results

) in order to avoid overlap with other projects using elementary in the same schema (we use developer-scoped working schemas). How can I accommodate this through configuration or command-line parameters supplied to

edr report

? Might there be a better way to solve this problem that doesn't involve renaming the elementary models?

A message from kapa.ai