`CheatSheetList` should be responsible for `Storage`, not `UI`

[k-walter]

As titled, it should not be the responsibility of UI to handle everything. For example, when CommandExecutor calls a method within CheatSheetList to edit an existing cheat sheet, Storage methods should be invoked within CheatSheetList to update if necessary.

[nus-pe-bot]

Team's Response

There are several operation that involves Storage class but does not involve CheatSheetList class, such as the Setting and the Favorite Command.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: In which case, it would be better if CheatSheetList, Setting and Favorite Command individually manage their Storage instances to reduce coupling.

• Eg program does not need to save favorites when editing their settings.
• The respective class methods that edit data should be naturally aware of whether to call Storage, rather than having UI make the decision.
• Making UI responsible for handling everything is similar to using global variables in your program.

---