This PR will result in the following new package version:
Breaking since the folder stripe_reports was renamed to stripe_financial_reports and could break if users relied on the old name.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
🚨 Breaking Changes 🚨
Renamed folder stripe_reports to stripe_financial_reports to be more descriptive of the contents.
⚠️ If you are using folder names to scope out configs, runs, etc., you will need to update the folder name.
Bug fixes
Updated model int_stripe__date_spine to accommodate cases when model stripe__balance_transactions has no records.
Previously, the date spine relied on stripe__balance_transactions to set date bounds, which caused errors if empty. Now, the model defaults to a one-month range in such cases.
Under the hood
Updated structure of model int_stripe__date_spine for improved performance and maintainability.
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)
Will regen after approval.
[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:
Validation tests pass.
If you had to summarize this PR in an emoji, which would it be?
PR Overview
This PR will address the following Issue/Feature:
70
77
This PR will result in the following new package version:
stripe_reports
was renamed tostripe_financial_reports
and could break if users relied on the old name.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:
If you had to summarize this PR in an emoji, which would it be?
🍓