Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Closes #2068 Updated
traceability_vars
toset_values_to
#2079Closes #2068 Updated
traceability_vars
toset_values_to
#2079Changes from 2 commits
ae842d2
0077aa9
5c40bcf
166de8d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@pharmaverse/admiral Wondering if we should rewrite the code-section as well to keep up with our current programming practices but otherwise I think it should be fine?
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.
Hey @bms63 @manciniedoardo @bundfussr Are you able to provide some feedback on @zdz2101 question above, or should I merge this PR for now and the question above could be address in a separate issue?
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.
@zdz2101 What do you mean by code-section? I'm not following :(
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.
@bms63 little two-parter, semi-related to function re-work type of stuff:
set_values_to
argument related stuff, we useprocess_set_values_to()
fromadmiraldev
dplyr::transmute()
was superseded earlier this year, we don't use it too often in our codebase anyhow but if we want to harmonize our code-base such that all functions are semi-consistently this is kinda part of itPersonal opinion, I'm okay with just merging this in, just thought I'd throw it out there. It'd probably be a back of the backlog type of task, kinda that mantra of don't fix wha'ts not broken type of thing
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.
My view is that harmonisation of the code base is important; within the harmonisation efforts priority should be given to user-facing harmonisation so that we can move faster towards admiral 1.0.0. Thus I don't mind if a change like this is relegated to the backlog and we get to it when we get to it.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.