-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
249 remove check for datanames
parameter being a subset of datanames(teal_data)
in get_code(teal_data)
#250
Conversation
… get_code(teal_data)
Code Coverage Summary
Diff against main
Results for commit: 060248c Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 14 suites 2s ⏱️ Results for commit 060248c. ♻️ This comment has been updated with latest results. |
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.
Now that datanames
is optional, I think the vignette should briefly mention what it is used for.
Co-authored-by: Aleksander Chlebowski <[email protected]> Signed-off-by: Marcin <[email protected]>
Co-authored-by: Aleksander Chlebowski <[email protected]> Signed-off-by: Marcin <[email protected]>
Sure, we can create a new issue for that |
Please open one and assign me to it. |
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.
👍
Created an issue here #251 |
Close #249
This PR removed a check in
get_code(teal_data)
that was veryfing ifdatanames
parameter is a subset ofdatanames(teal_data)
. Sincedatanames()
is now optional, we do not need to have this check, and we can allow to specify code extraction for any object inside the code.datanames() <-
calls from tests ofget_code()
datanames() <-
calls from examples ofget_code()