We've spoken about this many times, but why does project mark NEED to be able to mark multiple assignments together? Why can't it just be good at marking one assignment. The TAs still need to create the amount of work anyways, so the only difference that it is creating is that the marking process is done under one directory.
If TAs want to multiple assignments, they should git pull project mark into multiple places, each designated with their respective assignment, and then run them exclusive from each other. To me this small "benefit" doesn't justify the code complexity that it creates. It also confuses the future users.
Really needs to be discussed imo.
We've spoken about this many times, but why does project mark NEED to be able to mark multiple assignments together? Why can't it just be good at marking one assignment. The TAs still need to create the amount of work anyways, so the only difference that it is creating is that the marking process is done under one directory.
If TAs want to multiple assignments, they should git pull project mark into multiple places, each designated with their respective assignment, and then run them exclusive from each other. To me this small "benefit" doesn't justify the code complexity that it creates. It also confuses the future users.
Really needs to be discussed imo.