As part of the refactoring process, the next step is to create the specification for our ManagerHistory. This component will be responsible for implementing the add, remove, and replace functions, which will directly interact with the editor, affecting the user interface (UI). To facilitate code maintenance, we will use the "delegator" pattern, allowing for more granular management of these functions by filtering based on undo and redo actions.
Objective
[ ] Define the ManagerHistory class to store the core functions.
[ ] Define the draft of the add, remove, and replace core functions.
[ ] Create the delegator method to identify the actions and call the core functions according to the specified operations in the jsonPatch object.
Context
As part of the refactoring process, the next step is to create the specification for our
ManagerHistory. This component will be responsible for implementing theadd,remove, andreplacefunctions, which will directly interact with the editor, affecting the user interface (UI). To facilitate code maintenance, we will use the "delegator" pattern, allowing for more granular management of these functions by filtering based onundoandredoactions.Objective
ManagerHistoryclass to store the core functions.add,remove, andreplacecore functions.delegatormethod to identify the actions and call the core functions according to the specified operations in thejsonPatchobject.