Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Namespacing: scope & resolution changes for vars & macros #3572

Closed
Tracked by #3362
jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3605
Closed
Tracked by #3362

Namespacing: scope & resolution changes for vars & macros #3572

jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3605
Assignees
@jtcohen6
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Milestone
dbt Core v1.6 Doc...

Comments

@jtcohen6
Copy link
Collaborator

jtcohen6 commented Jun 20, 2023 •
edited
Loading

Pages requiring update (of one sort or another):

Relevant dbt-core PRs:
@jtcohen6 jtcohen6 mentioned this issue Jun 20, 2023
Closed
@jtcohen6 jtcohen6 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear idea Proposes an idea for new content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) labels Jun 20, 2023
@jtcohen6 jtcohen6 added this to the dbt Core v1.6 Documentation milestone Jun 20, 2023
This was referenced Jun 22, 2023
Merged
Merged
@runleonarun runleonarun added the priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows label Jun 22, 2023
@jtcohen6 jtcohen6 self-assigned this Jun 24, 2023
jtcohen6 added a commit that referenced this issue Jun 28, 2023
@jtcohen6 @matthewshaver
Updates to var, global macro resolution rules for package resources (#…
cab7a3f 
…3605)

resolves #3572

## What are you changing in this pull request and why?

- Update variable precedence rules, for resources in packages that are
calling variables
- Copied a lot of
dbt-labs/dbt-core#7509 (review)
into the docs on macro `dispatch`, and linked to that new subsection
from `generate_x_name` pages

These are "quick hits," and _very_ low-lying changes. For the people who
have had to go deep on this stuff (package maintainers), I hope they're
a big improvement to consistency/flexibility. I expect the vast majority
of people to have no idea what these things mean.

## Checklist
Uncomment if you're publishing docs for a prerelease version of dbt
(delete if not applicable):
- [x] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [x] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [x] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

---------

Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
@runleonarun runleonarun removed the idea Proposes an idea for new content label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jtcohen6 jtcohen6

Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Projects
None yet
Milestone
dbt Core v1.6 Documentation
Development

Successfully merging a pull request may close this issue.

Updates to var, global macro resolution rules for package resources dbt-labs/docs.getdbt.com
2 participants
@runleonarun @jtcohen6