-
Notifications
You must be signed in to change notification settings - Fork 6
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
Documentation: Examples of when to use Default and Permitted Values #72
Comments
This came up in our admiralonco tester feedback: Comparing for example https://pharmaverse.github.io/admiralonco/test/reference/derive_param_bor.html#arguments with https://pharmaverse.github.io/admiralonco/test/reference/derive_param_confirmed_bor.html#arguments we got the feedback: Fully agree with making this update to include them consistently across all functions. |
See summary of discussions pharmaverse/admiralonco#130 as these updates from admiralonco will also be needed across admiral functions. @bms63 will summarize these in the programming strategy so we have a clear guide to follow: #64 |
Moving this to admiraldev |
Created a table of functions in admiral (43 impacted) which has at least 1 argument/param that contains the following in the roxygen block: Table contains 4 columns:
|
omg @zdz2101 thank you for taking this on!!! |
@zdz2101 can you break this into separate issues:
|
Please select a category the issue is focused on?
Function Documentation
Let us know where something needs a refresh or put your idea here!
A good part of our function documentation have default and permitted values listed in the function arguments. However, this is not completely adopted across
admiral
.To remedy this:
The text was updated successfully, but these errors were encountered: