OfflineContentManager import_content does not create folder
Open
bug
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 1.2k
- Avg merge
- 2h 40m
- Merged PRs (30d)
- 2
Description
In version 2.4.2, for OfflineContentManager's import_content method, if you specify a folder that does not exist it does not create the folder for you, and the imported content ends up in the user's root folder.
To reproduce the issue, specify a folder name that does not exist in import_content.
The expected behavior is for the folder to be created, if it does not exist, and for the imported content to end up in that new folder.
Contributor guide
Assessment
This issue has not been assessed yet.