Closed chuckleong21 closed 4 years ago
Hi @chuckleong21 , thank you for your proposals! I am currently involved in some other projects and I have not a lot of time left for polishing things up here on updateR. Nevertheless I think this is a useful tool for the #Rstats community so it would be great if you could help make it even more functional and useful.
So: welcome on board!
Which kind of clarifications do you need? How can I help you?
Thanks
What was the intent for file
argument in updateR()
? I found the argument was redundant in the tidying process: if users feel that there is a need to supply file
argument with a local file path or a direct link of the file, it does somehow swing from the goal of {updateR} -- update R with a single command.
updateR()
should handle the actions above properly inside R alone.
Hi, @AndreaCirilloAC . Interesting and amazing work! So I took a look at the codes in
updateR.R
. I found it a bit messy and helper functions are needed to make things look organized. For example,latest_r_version()
returns a list containing elements that come in handy for executables inupdateR()
:list_packages()
returns a vector of package names filtered out the base ones.ask_password()
utilisesreadline()
to guide useRs to enter admin password upon prompt message instead of feeding straight away into the oldadmin_password
argument and exposing it in the global environment.check_compactability()
specially responses to the situation where a user runs R 3.6 and macOS 10.12.x and wants to use updateR. In this case,check_compactability()
will return the following error:Helper functions are not necessary to be exported and make them accessible to users and they use the package as before. But those functions make it easier to make changes and implement features in the future.
I could submit a pull request if you like my ideas here. But a little bit more information on the work done so far is needed to help me clarify some confusions.