Code refactoring using terms defined in our glossary
Some Python class and packages need to be renamed for a better compliance with the shared Terminology which provides a better understanding of Watcher objects and components by every contributor.
In some Python class, we need to provide more comments in order to explain what is each Watcher business object (Audit Template, Audit, Action Plan, ...).
We may also add some code inspection in order to automatically generate the Glossary from these comments.
Blueprint information
- Status:
- Complete
- Approver:
- Antoine Cabot
- Priority:
- High
- Drafter:
- Vincent Mahe
- Direction:
- Approved
- Assignee:
- Jean-Emile DARTOIS
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
- Implemented
- Milestone target:
- mitaka-2
- Started by
- Antoine Cabot
- Completed by
- Antoine Cabot
Related branches
Related bugs
Sprints
Whiteboard
we should define all terms in the glossary before refactoring the code
https:/
Gerrit topic: https:/
Addressed by: https:/
Code refactoring - Rename Command to Action
Gerrit topic: https:/
Addressed by: https:/
Code refactoring - Meta-Action -> Action
Gerrit topic: https:/
Addressed by: https:/
Code refactoring - Rename efficiency to efficacy
Gerrit topic: https:/
Addressed by: https:/
Code refactoring - Rename Primitive to Action
Addressed by: https:/
Code refactoring - Rename mapper to mapping
Addressed by: https:/
Code refactoring - Rename Mapper to Mapping
Addressed by: https:/
Tidy up - Rename Base
Gerrit topic: https:/
Addressed by: https:/
Missing space for pragma cover
Addressed by: https:/
Tidy up - Decision Engine
Addressed by: https:/
Rename command to audit
Addressed by: https:/
Remove useless event factory
Addressed by: https:/
Add Audit-template management in DefaultStrategy
Addressed by: https:/
Remove useless Meta-Action
Work Items
Dependency tree
* Blueprints in grey have been implemented.