You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request a feature that allows changing the main models directory name in the package, similar to how we can change the staging_folder_name using a variable. This would provide greater flexibility for structuring DBT projects, especially for teams that may follow different conventions or naming standards across projects.
Describe alternatives you've considered
The primary alternative is manually renaming the models directory, but this approach is not ideal as it requires adjustments in multiple parts of the project configuration. Additionally, manually changing the folder name may introduce issues with path references and the packages internal workings that expect the default directory name to be models.
Who will this benefit?
This feature will be useful for DBT users who have complex model directory structures or who need to follow specific naming conventions across multiple DBT projects.
For example:
Teams working across multiple DBT projects may want to standardise or differentiate folder names to improve clarity and maintainability.
Users following specific naming standards set by their organisation.
Are you interested in contributing this feature?
I'm interested in contributing this feature and would appreciate guidance on getting started.
The text was updated successfully, but these errors were encountered:
Isn't this a dbt_project.yml functionality by updating model-paths? I think by default it sets it to models, but you should be able to assign it multiple paths.
Describe the feature
I would like to request a feature that allows changing the main
models
directory name in the package, similar to how we can change thestaging_folder_name
using a variable. This would provide greater flexibility for structuring DBT projects, especially for teams that may follow different conventions or naming standards across projects.Describe alternatives you've considered
The primary alternative is manually renaming the
models
directory, but this approach is not ideal as it requires adjustments in multiple parts of the project configuration. Additionally, manually changing the folder name may introduce issues with path references and the packages internal workings that expect the default directory name to bemodels
.Who will this benefit?
This feature will be useful for DBT users who have complex model directory structures or who need to follow specific naming conventions across multiple DBT projects.
For example:
Are you interested in contributing this feature?
I'm interested in contributing this feature and would appreciate guidance on getting started.
The text was updated successfully, but these errors were encountered: