Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
Description:
When calling a method within the same class, there needs to be a separate Activation Bar to show that it is being called. (Refer to the areas marked in green)
Steps to Reproduce:
Open the user manual to the section Below is a sequence diagram that shows the flow of the implementation when a module is added by
Expected Result:
There should be a self-invocation activation bar at the area marked in green
Actual Result:
There is a lack of those activation bar
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
Description: When calling a method within the same class, there needs to be a separate Activation Bar to show that it is being called. (Refer to the areas marked in green)
Steps to Reproduce: Open the user manual to the section
Below is a sequence diagram that shows the flow of the implementation when a module is added by
Expected Result: There should be a self-invocation activation bar at the area marked in green
Actual Result: There is a lack of those activation bar
Screenshot:
Screenshot 2024-04-19 at 5.48.29 PM.png
[original: nus-cs2113-AY2324S2/pe-interim#2531] [original labels: severity.Low type.DocumentationBug]