Running a task should be executed in a temporary session, to not collide with projects in the current session with the same name.
We had the issue, assuming a project "MyProject" in Folder "A" is already in the session.
If now another project "MyProject" in Folder "B" is processed in the batch app, "MyProject" of Folder "A" is instead opened due to the name collision. Hence, all changes to the project will be done in the wrong folder.
Impact on the codebase
Only this batch command "run -f"
Current workarounds
In regression tests, we need to manually create temp session. This is ugly and slow.
Summary
Running a task should be executed in a temporary session, to not collide with projects in the current session with the same name.
We had the issue, assuming a project "MyProject" in Folder "A" is already in the session. If now another project "MyProject" in Folder "B" is processed in the batch app, "MyProject" of Folder "A" is instead opened due to the name collision. Hence, all changes to the project will be done in the wrong folder.
Impact on the codebase
Only this batch command "run -f"
Current workarounds
In regression tests, we need to manually create temp session. This is ugly and slow.