clarify cross project ref pages/headers #4695
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
jtcohen6
approved these changes
Jan 2, 2024
fold jeremy's feedback without changing header
mirnawong1
commented
Jan 2, 2024
mirnawong1
commented
Jan 2, 2024
|
Check your created Crawler Check your created index on your Algolia Application |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this pr adds or rewrites headers so 'cross project ref' is explicit for users and easier to search. previously there were no clear headers or sections on pages that referenced 'cross project ref' so it wasn't 100% clear where to read up on this.
the PR also adds keywords for better searching/discoverability.
Previously
For example, the following pages refer to 'ref' and were the main pages to read up on cross project ref. however it didn't explicitly state that:
https://docs.getdbt.com/docs/collaborate/govern/project-dependencies#how-to-use-refhttps://docs.getdbt.com/reference/dbt-jinja-functions/ref#two-argument-variantProposed
I'm now proposing to be more explicit in the headers by adding 'cross project ref or ref models':
/docs/collaborate/govern/project-dependencies#how-to-write-cross-project-ref/reference/dbt-jinja-functions/ref/#ref-project-specific-models