-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rewrite/reorganize contexts - now they are objects that have a to_dict() - special decorators on properties/methods to indicate membership - reorganize contexts/ to remove many many import cycles Context behavior changes: - 'dbt_version' is alwways available - 'target' is available as long as the profile has been parsed - 'project_name' is available in: query headers, hooks, models, and macro execution Profiles/projects now render at load time - reading a profile or project file requires a ConfigRenderer - projects get an extra-fiddly special load for use during initial parsing - it returns the profile name and a function that, given a renderer, can return the rest of the Project - idea is: use the profile name to load the Profile, use that to build a ConfigRenderer that has a TargetContext, render the project with that - profiles.yml is rendered with the 'base' context - dbt_project.yml/schema.yml/packages.yml are rendered with the 'target' context: 'base' context + 'target' - docs are rendered with the docs context: 'target' context + the 'doc' function - query headers are rendered with the query header context: 'target' context + macros + 'project_name' - executed macros/models should have the same context as previously (query headers + adapter/model/etc related functions) Moved actual ref/source searching into the manifest Moved the rest of the parse utils into parser/manifest.py Made the ref/source resolvers defined in the provider context a bit more sane/well-defined Picked consistent-but-not-great names for all the various context generation functions Moved write_node into ParsedNode
- Loading branch information
Jacob Beck
committed
Feb 6, 2020
1 parent
032d77d
commit b8febdd
Showing
58 changed files
with
2,000 additions
and
1,636 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.