-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix plurals in FoundStats message #9465
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9465 +/- ##
==========================================
+ Coverage 87.89% 87.90% +0.01%
==========================================
Files 164 164
Lines 21967 21966 -1
==========================================
+ Hits 19307 19310 +3
+ Misses 2660 2656 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests should pass now, thanks for adding this in!
resolves #9464
Problem
As part of moving the event system & log formatting logic into
dbt-common
, we introduced a "cosmetic regression" that prints the plural ofanalysis
asanalysiss
in theFoundStats
line.Solution
Following the new logic in
dbt_common.events.format.pluralize
, pass theNodeType
enum object intopluralize
, rather than its (manually mapped) string name.While this fixes the issue with
analyses
, it does mean that we'll be printing multi-word node types with an underscore instead of a space:I think that's fine — it's more consistent with how these appear elsewhere — and it's definitely better than
saved querys
;)Checklist