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

Documentation: Examples of when to use Default and Permitted Values #72

Closed
1 of 5 tasks
bms63 opened this issue Jul 6, 2022 · 6 comments · Fixed by #274
Closed
1 of 5 tasks

Documentation: Examples of when to use Default and Permitted Values #72

bms63 opened this issue Jul 6, 2022 · 6 comments · Fixed by #274
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@bms63
Copy link
Collaborator

bms63 commented Jul 6, 2022

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:

@bms63 bms63 added the documentation Improvements or additions to documentation label Jul 6, 2022
@rossfarrugia
Copy link
Collaborator

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:
the "Arguments" documentation is not same across all functions: for eg "derive_param_bor" had provided if the parameter is required or not. but if we look into consistency across all references to provide permistted values, optional or not, defualt values.

Fully agree with making this update to include them consistently across all functions.

@rossfarrugia
Copy link
Collaborator

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

@bms63
Copy link
Collaborator Author

bms63 commented Sep 6, 2022

Moving this to admiraldev

@bms63 bms63 transferred this issue from pharmaverse/admiral Sep 6, 2022
@thomas-neitmann thomas-neitmann removed their assignment Oct 5, 2022
@zdz2101 zdz2101 self-assigned this Nov 4, 2022
@zdz2101
Copy link
Collaborator

zdz2101 commented Nov 4, 2022

Created a table of functions in admiral (43 impacted) which has at least 1 argument/param that contains the following in the roxygen block:
*Default*
*Permitted Values*

functions_to_check.csv

Table contains 4 columns:

  • the file that contains the function
  • the function in question
  • logical for if it contains default
  • logical for if it contains permitted

@bms63
Copy link
Collaborator Author

bms63 commented Nov 4, 2022

omg @zdz2101 thank you for taking this on!!!

@bms63
Copy link
Collaborator Author

bms63 commented May 8, 2023

@zdz2101 can you break this into separate issues:

  1. Clean up functions in admiral and admiraldev based on guidance developed in programming strategy (contingent on updates from Adam)
  2. Create the guidance itself in the programming strategy

zdz2101 pushed a commit that referenced this issue May 18, 2023
zdz2101 pushed a commit that referenced this issue May 18, 2023
zdz2101 pushed a commit that referenced this issue May 19, 2023
zdz2101 added a commit that referenced this issue May 31, 2023
…oc_updates@devel

Closes #272, #253, #72 continues deprecation process and adds some doc updates
@bms63 bms63 closed this as completed Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
4 participants