Open theodorekwok opened 2 years ago
This is indeed a bug, however, this is a very low severity bug since SetCaloriesCommand is called from the :Parser class, and therefore doesn't affect the implementation of SetCaloriesCommand at all.
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: Severity VeryLow are for purely cosmetic issues. This issue pointed out relates to the correctness of the UML diagram. This will interfere with the reader when the reader is reading this diagram along with the reference to the codebase. Therefore as it pertains to the correctness and accuracy of the seq diagram, its error has nothing to do with it being a cosmetic.
From the code, it is setParse that calls the SetCaloriesCommand constructor method not parseMaster()