Fix exposure parsing to allow other resources with the same name #3009
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
kwigley
force-pushed
the
fix/exposure-parsing
branch
from
f03438a
to
c14e6f4
Compare
kwigley
force-pushed
the
fix/exposure-parsing
branch
from
2eb3ec0
to
f9e1f4d
Compare
gshank
approved these changes
Jan 13, 2021
jtcohen6
approved these changes
Jan 14, 2021
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.
resolves #2969
Description
Exposure parsing occurs after all other node types have been parsed. #2920 made exposures "documentable" which caused this node type to be parsed twice. Once with
TestablePatchParserand once with the appropriateExposureParser. This PR skips theTestablePatchParserstep.Checklist
CHANGELOG.mdand added information about my change to the "dbt next" section.