Allow documenting custom materializations in `.yml` files

Describe the feature

Allow documenting custom materializations in .yml files

Describe alternatives you’ve considered

Currently I’m defining materializations as a list of materializations in a .yml file to have it documented in the same pull request as my code.

Additional context

There are no specs about materialization documentation as far as I know. There are for macros, for example: https://docs.getdbt.com/reference/macro-properties/. But if you define materializations as macros then dbt will warn you with: WARNING: Found documentation for macro "your_materialization" which was not found.

Who will this benefit?

All dbt users will benefit if all object types in dbt can be documented in a consistent way.

Are you interested in contributing this feature?

Let us know if you want to write some code, and how we can help.

[ilmari-aalto]

I still think this is relevant - commenting so it won’t be closed

[github-actions[bot]]

Although we are closing this issue as stale, it’s not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.