{"push_id":2682829872,"size":1,"distinct_size":1,"ref":"refs/heads/670-decouple-undoablecommand-addressbook","head":"3cb4f697663d1fac7280f5bc039199d5971a7136","before":"ce3987ed97fc6b21aafa72569b1f9aa8a0176b7a","commits":[{"sha":"3cb4f697663d1fac7280f5bc039199d5971a7136","author":{"name":"Jun An","email":"fcaf5ab6d2992fbdea7603c4d2e176a2103cf7fa@u.nus.edu"},"message":"DeveloperGuide: update section of UndoRedoStack to VersionedAddressBook\n\nThe app previously uses UndoRedoStack which stores the UndoableCommands\nin LogicManager for the undo/redo mechanism.\n\nSince the undo/redo machanism has been shifted to VersionedAddressBook\nwhich stores ReadOnlyAddressBook in a List, and has been moved to Model\nlayer instead, the sections on undo/redo feature, Logic and Model\ncomponent in DeveloperGuide is out of date.\n\nAlso, commands that do not mutate the address book, such as\nFindCommand and ListCommand, will no longer clear the redoable\naddress book states. This allows for redo commands to pass when we\nundo commands and execute a non-mutating command afterwards.\n\nUndoableCommand has also been removed from the codebase as well.\n\nLet's update the out of date sections in the DeveloperGuide, such\nas switching from UndoRedoStack to the updated VersionedAddressBook,\nhow the undo/redo mechanism works, and remove any reference\nto UndoableCommand in DeveloperGuide.","distinct":true,"url":"https://api.github.com/repos/yamidark/addressbook-level4/commits/3cb4f697663d1fac7280f5bc039199d5971a7136"}]}
{"actor":{"display_login":"yamidark"}}