-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shorten field descriptions #11
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working through this @fivetran-reneeli! There are just a few updates needed before this is good to go. Once these are applied feel free to regen the docs and let me know it is ready for re-review.
Thanks!
integration_tests/dbt_project.yml
Outdated
models: | ||
+persist_docs: | ||
relation: true | ||
columns: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add the databricks conditional logic to be consistent across implementations.
models: | |
+persist_docs: | |
relation: true | |
columns: true | |
models: | |
+persist_docs: | |
relation: "{{ false if target.type in ('spark','databricks') else true }}" | |
columns: "{{ false if target.type in ('spark','databricks') else true }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the updates @fivetran-reneeli. I do have one small clarifying question about the new description for source_type as it seems we are missing some types that were in the original. Can you update the description to match the previous types. Or if they were removed intentionally, please share the reasoning.
Once the description is updated or the reasoning is provided, this will be good to go!
models/docs.md
Outdated
- App Clip: Users tapped a link in your App Clip that brought them to your App Store product page. If the user then downloaded your app, the resulting Download is attributed to your App Clip as the source. | ||
- Web Referrer: Users tapped a link from a website that brought them to your App Store product page. If a chain of redirects in Safari leads to your App Store product page, the referring website will be the last URL in the chain. | ||
- Null: This is the default value for data that does not provide source types, including: crashes, subscription events and subscription summary. | ||
There are five types of sources: App Store Browse, App Store Search, App Referrers, Web Referrers, and App Clips. Null is the default value for data that does not provide source types, including: crashes, subscription events and subscription summary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mention there are 5 types; however, it looks like the original description had 8. Were the three other intentionally removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm that's true... when I went on the apple store docs, this is what is said basically verbatim
https://developer.apple.com/app-store/measuring-app-performance/
But if I click on the link for more info it does reference Unavailable, Institutional Purchases, and Null. I'll add these in, better to catch more just in case
PR Overview
This PR will address the following Issue/Feature:
fivetran/dbt_app_reporting#18
This PR will result in the following new package version: v0.3.1
Updates the description for field
source_type
to reduce the number of characters. As such this is not a breaking change.Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
See above
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":
View new docs
Standard Updates
Please acknowledge that your PR contains the following standard updates:
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?
💃