feature/api-v3-updates - #6
Conversation
fivetran-joemarkiewicz
left a comment
There was a problem hiding this comment.
@fivetran-catfritz thanks for working through these updates. I do have a few inline comments below that should be addressed before approving. Primarily, I would request we remove the in join casting in place of performing those within the staging models. Let me know if you want to discuss this in more detail. Thanks!
| # - package: fivetran/amazon_ads_source | ||
| # version: [">=0.2.0", "<0.3.0"] | ||
|
|
||
| - git: https://github.com/fivetran/dbt_amazon_ads_source.git | ||
| revision: feature/api-v3-updates | ||
| warn-unpinned: false |
There was a problem hiding this comment.
Reminder to update before merge and release.
|
This is ready for re-review. |
fivetran-joemarkiewicz
left a comment
There was a problem hiding this comment.
@fivetran-catfritz thanks so much for working through these updates! I just have two small comments that I would like your eyes on. Once you take a look and make any minor updates, this is good to go!
As these are very minor comments, I am happy to approve this PR!
PR Overview
This PR will address the following Issue/Feature: fivetran/dbt_amazon_ads_source#9
This PR will result in the following new package version:
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
🎉 Features
🚘 Under the Hood
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 acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":
Standard Updates
Please acknowledge that your PR contains the following standard updates:
DECISIONLOG updates have been updated (if applicable)Appropriate yml documentation has been added (if applicable)dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:
If you had to summarize this PR in an emoji, which would it be?
💃