This PR will result in the following new package version:
v0.10.0 breaking because of deprecation
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
🚨 Breaking Changes 🚨
The parameter full_statement_version=false has been fully sunset from the sfdc_formula_view macro. You will now need to remove this parameter to avoid a compilation error.
Under the hood
Included auto-releaser GitHub Actions workflow to automate future releases.
Updated maintainer pull request template.
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
[x] dbt run –full-refresh && dbt test
[ ] ~dbt run (if incremental models are present) && dbt test~
Before marking this PR as "ready for review" the following have been applied:
[x] The appropriate issue has been linked, tagged, and properly assigned
[x] All necessary documentation and version upgrades have been applied
[x] docs were regenerated (unless this PR does not include any code or yml updates)
[x] BuildKite integration tests are passing
[x] Detailed validation steps have been provided below
Detailed Validation
Please share any and all of your validation steps:
Consistency tests pass
When setting full_statement_version=false in a model, a compilation error is successfully thrown.
Additional notes
full_statement_version=true continues to be allowed so that users do not experience the below compilation failure since the macro cannot take an unexpected argument.
If you had to summarize this PR in an emoji, which would it be?
PR Overview
This PR will address the following Issue/Feature:
105
This PR will result in the following new package version:
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
Consistency tests pass
When setting
full_statement_version=false
in a model, a compilation error is successfully thrown.Additional notes
full_statement_version=true
continues to be allowed so that users do not experience the below compilation failure since the macro cannot take an unexpected argument.If you had to summarize this PR in an emoji, which would it be?
:dancer: