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

Function exposure #87

Open
clnsmth opened this issue Oct 25, 2019 · 1 comment
Open

Function exposure #87

clnsmth opened this issue Oct 25, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@clnsmth
Copy link
Member

clnsmth commented Oct 25, 2019

From @wetlandscapes email:

How many of the underlying functions should we expose to the user? That is, this package really only has one function that a user will likely care about: datapie_shiny(). But if you look at the documentation, there are a bunch of other (very crafty) functions. However, if we want to encourage use of this package, it may be worth simplifying the R interface by just focusing in on a single datapie_shiny function (and possibly renaming the function to just datapie to help enforce its singular utility). This would also have the benefit of reducing conflicts between other packages (which is generally a good thing). That said, I think internal documentation of functions is still very worth it (for development sanity). Anyhoo, just some thoughts.

@clnsmth clnsmth added the enhancement New feature or request label Oct 25, 2019
@atn38
Copy link
Member

atn38 commented Oct 25, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants