Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3012 +/- ##
=======================================
Coverage 99.23% 99.23%
=======================================
Files 128 128
Lines 7288 7288
=======================================
Hits 7232 7232
Misses 56 56 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bisaloo
left a comment
There was a problem hiding this comment.
Thanks, I think it's a helpful change! I left two minor comments.
Would it be worth testing it in another PR before merging?
| all_locales_passed <- TRUE | ||
| for (LOCALE in c("C", "en_US.utf8", "hu_HU.utf8", "ja_JP.utf8")) { | ||
| check_roxygenize_idempotent(LOCALE) | ||
| all_locales_passed <- check_roxygenize_idempotent(LOCALE) && all_locales_passed | ||
| } |
There was a problem hiding this comment.
The switch between looking at "what failed" in check_roxygenize_idempotent() vs "what passed" here is not the most straightforward to resonate about IMO.
There was a problem hiding this comment.
Yea I think that's me being too cute to save 2 lines.
There was a problem hiding this comment.
No, sorry, I wasn't clear. I think what you changed was perfectly reasonable.
I highlighted the fact we use any_failed inside check_roxygenize_idempotent() to all_locales_passed outside. It requires some mental gymnastics when thinking about the code, to make the boolean negation.
I would use all_passed (rather than any_failed) inside check_roxygenize_idempotent() or any_locale_failed in the for loop here.
Does this make sense?
(More generally, and slightly off-topic, I would likely generally consider that using ! in an return() is likely a code smell for readability. Maybe a linter could make sense.)
Good idea! I'd tested locally, but it's good for transparency to have it in the public logs. #3013 |
Closes #2931. Co-written with Gemini.