-
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
Why functions in helper_function.R
are exported?
#253
Comments
Sure, it might be productive to prioritize functions that are not currently used anywhere in code examples and vignettes, as it would require non-trivial changes to the code examples and vignette to un-export previously exported functions. Or do you mean we need one (or multiple) more accurate file name(s) + section name(s) to organize these functions instead of simply using the generic term "helper"? |
Feel those functions should not be exported to user. For example, why would a user need |
Sure, that makes sense. My point was, https://merck.github.io/gsDesign2/articles/usage-gs-spending-bound.html So they need to be rewritten or removed to un-export |
Got it. If that's the only reason to keep them exported. Let me find way to rewrite them. btw, would you feel vignettes is OK to refer internal function if we did not submit the vignettes to CRAN? (Given some vignettes is to discuss internal logic derivation for technical details) |
Sounds great. And good point - it might be ok to use |
Decision: we will keep the following functions exported: And we can un-export the following functions: |
Let's work on this issue when #261 is merged. |
Please review the diff, examples has been udpated. |
Could we review if it is necessary to export helper functions?
https://merck.github.io/gsDesign2/reference/index.html#low-level-helpers
The text was updated successfully, but these errors were encountered: