Current behaviour in Repo.ts for downloadRepository() assumes that the string in the repoSave text field is a relative path from the application's root directory (e.g. C:......\VisualGit_SE701_2019_4). This is confusing as the "Change Save Directory" button populates the text field with a full file path, meaning text format is inconsistent between use cases (using a default location vs specifying a custom location).
The current implementation only works for relative paths, and will create a malformed file path if you attempt to specify a custom location, preventing you from cloning repos to the desired location.
Current behaviour in Repo.ts for
downloadRepository()assumes that the string in therepoSavetext field is a relative path from the application's root directory (e.g. C:......\VisualGit_SE701_2019_4). This is confusing as the "Change Save Directory" button populates the text field with a full file path, meaning text format is inconsistent between use cases (using a default location vs specifying a custom location).The current implementation only works for relative paths, and will create a malformed file path if you attempt to specify a custom location, preventing you from cloning repos to the desired location.