Skip to content

Adding macros support #139

@Romanananan

Description

@Romanananan

Hi there 👋
First, thank you for creating and supporting dbt-score, it's a great tool and really helps to impose dbt dev standards in a very concise and convenient way.

But currently, there is no option to run a macros validation. I think that macros also must be in order and follow certain standards, as with other parts of dbt project.

In manifest.json macros is presented in the way as other entities; it has fields: 'name', 'resource_type', 'package_name', 'path', 'original_file_path', 'unique_id', 'macro_sql', 'depends_on', 'description', 'meta', 'docs', 'patch_path', 'arguments', 'created_at', 'supported_languages'. Thus, all of it can be validated using dbt-score.

I believe it would be great to be able to validate macros the same way now we validate Models, Sources, Seeds, etc.
The perspective usage can be smth like dbt-score lint --select macros:<my_macro>. Essentially, in the same way as other entities.

What do you think of that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions