Import to instance goes to wrong place #217
Assignees
Labels
Comments
csatt
added a commit
that referenced
this issue
Aug 5, 2023
import_results() method: If import is to an instance, set the copy destination to the import folder itself instead of its parent. get_dest_dir() method: if destination is an instance, don't add the app name or source directory instance path. display_copy_summary() method: display the correct path (don't append IV_Swinger2) if the destination is an instance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an obscure bug. I found it while testing the pathlib refactor, but it exists in the released app.
Repro:
The dialog confirms the copy, but the destination path is something like:
/Users/csatt/Library/Application Support/IV_Swinger2/inst/IV_Swinger2
That isn't where it should go, and it isn't visible from the Results Wizard.
It's a little strange to be importing runs into an instance, but there's a use case: There could be runs that were performed before the instance was created, but belong to that instance. The user would want to import them into the instance.
The fix should be to just import runs to the instance folder.
The text was updated successfully, but these errors were encountered: