-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rename reports
to exposures
#2777
Labels
enhancement
New feature or request
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
We've had several conversations internally since #2730. While concrete,
report
names only a subset of the intended functionality of the new node type. We're going back to the original name,exposure
, because:Describe alternatives you've considered
Other names we considered:
Additional context
All functionality is identical. The only proposed change is replacing all instances of
report(s)
withexposure(s)
.Future functional changes to the
exposures
node, out of scope here:tags
, such thatdbt ls -s tag:common_tag
will return all sources, models, tests, and exposures that havecommon_tag
Who will this benefit?
Names are important, naming things is hard. We want to be using the best words we can when it's time to put this in front of dbt developers.
The text was updated successfully, but these errors were encountered: