Open duynguyen24501 opened 3 years ago
This is an intended behaviour as we did not intend entry's description/tag to be super long. As a business owner, a description of an expense or revenue does not necessarily need to be very long. (no need for proper sentence structure etc) Likewise for tags as well. Additionally, the Tag class and Ui aspect regarding Tag remained unchanged from AB-3. So its display and functionality is inherited from AB-3
Team chose [response.Rejected
]
Reason for disagreement: The UI changed from full width (as AB3) to shorter width. Besides, there are up to two small lists in the window. As such, the chance that the tags overflow is very high to the users. Thus, the display is much different from AB3, so I believe team cannot take AB3 inheritance as defense argument.
Therefore, I decide to reject team response.
For add command, when I type a relatively large tag, the tag is overflowed out of the screen. The user cannot see the tag even when I enlarge to full screen.