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
Copy file name to clipboardExpand all lines: NEWS.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,26 @@
1
1
> Notes: the # between parenthesis refers to the related issue on GitHub, and the @ refers to an external contributor solving this issue.
2
2
3
+
4
+
# golem 0.5.1 to 0.6.0
5
+
6
+
## Breaking change
7
+
8
+
- Creating a `golem` doesn't call `set_here()` nor `usethis::create_project()` anymore. It used to be because we wanted to be able to use `here::here()`, but the function should be able to find its way based using `DESCRIPTION`. It gives a lighter implementation of golem projects creation as it doesn't mess up with where `here()` is anymore.
9
+
10
+
- The `add_*_files` and `use_*_files` now fail when:
11
+
- The directory where the user tries to add the file doesn't exist. `{golem}` used to try to create the directory but that's not the function job — use_*_file functions should only be there to add file (Singe responsabily )
12
+
- The file that the user tries to create already exists
13
+
14
+
- Creating a golem with `create_golem(overwrite = TRUE)` will now __delete the old folder__ and replace with the golem skeleton.
15
+
16
+
## Bug fix
17
+
18
+
- Removing the comments on golem creation didn't work fully, this has been fixed.
19
+
20
+
## Internal changes
21
+
22
+
- Full refactoring of the `add_*_files` and `use_*_files` functions that now all share the same behavior
23
+
3
24
# golem 0.5.1
4
25
5
26
* Hotfixing a bug with utils_download_file (#1168)
0 commit comments