Open nus-se-script opened 1 week ago
This is actually covered as a whole by the logic component of the DG. Match, screen and view company do not utilise a different sequence than what was shown, and creating diagrams for the implementation of each command might end up making the DG too long and hinder the reader instead. We believe that the time spent to create diagrams will not benefit future teams as much as putting that time to other improvements since they will still need to perform code tracing to understand how the actual implementation is done. Therefore, we consider this issue as not in scope.
--
There is no specific implementation for any features.
This can greatly hinder the development of future teams. Future development teams will be unsure of features that are newly added, such as:
[original: nus-cs2103-AY2425S1/pe-interim#3862] [original labels: severity.Low type.DocumentationBug]