Ticket	Summary	Owner	Status	Type	Component	Priority	Effort	Importance
#153	PRO_CHANGE_COMPOSING_R0	peko	closed	planned_task	PRO_LIB_ENTITIES	3	1	10
Reported by Astea, 4 years ago.
Description	wiki page: PRO_CHANGE_COMPOSING_R0 - effort: 1d
Analysis_owners	peko
Analysis_reviewers	orliin
Analysis_score	3.5
Design_owners	meddle
Design_score	0
Imp._owners	meddle
Imp._score	0
Test_score	0

Analysis

Overview

This task is about composite changes. Such changes are constructed of a list of simple changes.

Task requirements

• Review code GroupChange which represent a composite change.
• View also the things in Classes connected with changes.
• Make sure composite changes are properly created.
• Write unit tests and review the already written such unit tests.
• Provide examples when composing changes should be done - for example when the user hits the space key, a new character is entered and this is a simple change. On the other hand entering a word is a set of characters that should be undone as a GroupChange.
• Composing changes should be undone properly as well.
• NOTE pay special attention to the following task since for GroupChanges it is vital => PRO_CHANGE_TRANSACTION_SAFETY_R0

Task result

• Source code.
• List of composite changes in the wiki and the way a composite change is created.

Implementation idea

• review source code.
• think what should be improved and do it.
• provide more unit tests.
• think of the examples that should be composite changes.

Related

PRO_CHANGE_PRIMITIVES_R0
PRO_CHANGE_TRANSACTION_SAFETY_R0
PRO_CHANGE_COMMONS_R0
PRO_CHANGE_MANAGER_R0

How to demo

Design

Implementation

Testing

Comments