-
-
Notifications
You must be signed in to change notification settings - Fork 19
tm_t_summary* hide NAs when useNA = "no"
#1438
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
Conversation
Unit Tests Summary 1 files 71 suites 11s ⏱️ Results for commit f4bb51f. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 21ed094 ♻️ This comment has been updated with latest results. |
averissimo
left a comment
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.
|
averissimo
left a comment
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.
It looks fine as it is! It corrects the behavior and is more consistent across modules.
- 👍 You have the ok to merge **after** updating the
NEWSfile. - I have 1 more comment about consistent naming, but that is not a blocker



Pull Request
Fixes #1437
df_explicit_na()expression is only added whenuseNA = "ifany".Check also with tern issue: insightsengineering/tern#1440
To check run the app test and check the output has NAs only if
ifanyis selected on the UI.I haven't added specific tests for this. Probably a
shiny::testServerwith a snapshot could work to check that the table returns these rows.App to test