Open lacedaemon98 opened 4 years ago
Thank you for this question, my team has considered about this when we developed the application. We make use of the hashmap instead of list to store all the accounts, this decision helps to add other account operations. So to us, this is not a flaw, it is something we trade for time complexity.
Team chose [response.Rejected
]
Reason for disagreement: After renaming something (e.g account number 3) to something else, the user would likely want to list all the accounts again to check if the renaming was done properly. In this case, wouldn't it be very confusing for the user to find that the whole list of account jumble up?
I think that this behaviour should be documented (especially in the DG) if you want to trade for time complexity to let the user understand better.
Order of account list always get changed randomly when I add new account or rename an account. For example, when I added 3 accounts test, test1 and test3 consecutively, the list show this