Closed anarchuser closed 3 years ago
Actually, there is probably no need for the first method; thus, it makes more sense to give MoveMistakes the color as property and change the first method into documentation
I would like to prevent coupling code that doesn't have to be coupled, i.e. not add the color as property.
seems reasonable. I'm going to rework this anyways, though - It probably makes sense to construct InvalidMoveExceptions with MoveMistakes and Moves (the latter already contains information on the color, anyways)
It could have a method taking a Team or Color and return a message saying who violated how, i.e.:
Related to https://github.com/CAU-Kiel-Tech-Inf/gui/issues/7