You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
path Character string. Subdirectory in which to place the new module code file. The default is the current working directory.
However, when creating a new module the default path is actually the cache path
> getwd()
[1] "C:/Users/Tati/Documents/GitHub/EFI_webinar"
> SpaDES.core::newModule("testModule")
New module testModule created at C:/Users/Tati/Documents/GitHub/NWT/cache/tmp/RtmpqWw5f7/SpaDES/modules
(...)
> SpaDES.core::getPaths()
$cachePath
[1] "C:/Users/Tati/Documents/GitHub/NWT/cache/tmp\\RtmpqWw5f7/reproducible/cache"
(...)
In my opinion, the documentation expresses the correct behavior, and the module should be created in the current working directory, except if this would break any further functionalities (which I don't believe, but who knows)
The text was updated successfully, but these errors were encountered:
tati-micheletti
changed the title
Either documentation or default is wrong
Either documentation or default is wrong: newModule()Apr 11, 2024
I remember this conversation a while ago. I agree with @tati-micheletti . The default should not be random, but current directory. When it is random, the user can easily, accidentally, lose their work without realizing it.
Documentation of newModule says:
However, when creating a new module the default path is actually the cache path
In my opinion, the documentation expresses the correct behavior, and the module should be created in the current working directory, except if this would break any further functionalities (which I don't believe, but who knows)
The text was updated successfully, but these errors were encountered: