Skip to content
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

Run verification check when check is TRUE #281

Closed

Conversation

vedhav
Copy link
Contributor

@vedhav vedhav commented Jan 25, 2024

Part of insightsengineering/teal#1069

Please make sure that you also use the teal branch 1069-fix-code-warnings-when-data-is-verified@main for testing the example from the issue.

Copy link
Contributor

github-actions bot commented Jan 25, 2024

Unit Tests Summary

  1 files   14 suites   2s ⏱️
175 tests 173 ✅ 2 💤 0 ❌
244 runs  242 ✅ 2 💤 0 ❌

Results for commit 740aae7.

♻️ This comment has been updated with latest results.

Copy link
Contributor

badge

Code Coverage Summary

Filename                         Stmts    Miss  Cover    Missing
-----------------------------  -------  ------  -------  ------------------
R/cdisc_data.R                       1       0  100.00%
R/default_cdisc_join_keys.R         11      11  0.00%    16-34
R/deprecated.R                      57      57  0.00%    19-344
R/dummy_function.R                   2       2  0.00%    14-15
R/formatters_var_labels.R           36      11  69.44%   60, 69-80
R/join_key.R                        38       0  100.00%
R/join_keys-c.R                     12       0  100.00%
R/join_keys-extract.R              128       0  100.00%
R/join_keys-names.R                 15       0  100.00%
R/join_keys-parents.R               30       0  100.00%
R/join_keys-print.R                 45       0  100.00%
R/join_keys-utils.R                 73       3  95.89%   35-38
R/join_keys.R                       21       0  100.00%
R/teal_data-class.R                 25       1  96.00%   69
R/teal_data-datanames.R             10       0  100.00%
R/teal_data-get_code.R              14       0  100.00%
R/teal_data-show.R                   4       4  0.00%    14-19
R/teal_data.R                       25       9  64.00%   35, 44-50, 53
R/testhat-helpers.R                 26       0  100.00%
R/topological_sort.R                32       0  100.00%
R/utils-get_code_dependency.R      166       1  99.40%   258
R/verify.R                          42      11  73.81%   63, 93-97, 100-104
R/zzz.R                             10      10  0.00%    4-16
TOTAL                              823     120  85.42%

Diff against main

Filename          Stmts    Miss  Cover
--------------  -------  ------  --------
R/cdisc_data.R        0      -1  +100.00%
R/teal_data.R        +3       0  +4.91%
TOTAL                +3      -1  +0.18%

Results for commit: 740aae7

Minimum allowed coverage is 80%

♻️ This comment has been updated with latest results

@gogonzo
Copy link
Contributor

gogonzo commented Jan 25, 2024

@vedhav check shouldn't be used anymore - vignette about reproducibility shows only one way to verify object https://insightsengineering.github.io/teal.data/main/articles/teal-data-reproducibility.html

check should be deprecated with the link to the migration page insightsengineering/teal#988

@vedhav
Copy link
Contributor Author

vedhav commented Jan 25, 2024

Got it. So, do you recommend creating a teal_data wrapper function that we just internally use in teal which has a way to check?
Because I can't think of another way to verify a new teal_data object that we pass into the modules.

@gogonzo
Copy link
Contributor

gogonzo commented Jan 25, 2024

Got it. So, do you recommend creating a teal_data wrapper function that we just internally use in teal which has a way to check? Because I can't think of another way to verify a new teal_data object that we pass into the modules.

No, we won't reverify data. Here check has to be deprecated and in teal I've provided a solution in the review

@vedhav
Copy link
Contributor Author

vedhav commented Jan 25, 2024

In this case, Shall we add a r lifecycle::badge("deprecated") and hint that they have to use verify method now?

@gogonzo
Copy link
Contributor

gogonzo commented Jan 25, 2024

closing this PR in favour of
#282

@gogonzo gogonzo closed this Jan 25, 2024
@gogonzo gogonzo deleted the 1069-fix-code-warnings-when-data-is-verified@main branch January 25, 2024 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: The verification status of the teal_data object is lost making all data to be unverified
2 participants