When do we need to repair concern graphs?
When the source code is changed after a concern is already maded based on this code. In other words, a concern graph is a collection of some of the facts about the source code. When the source code is changed after the concern graph is created, the facts stored in a concern may not be true anymore. That's where inconsistencies come into play.
When a concern is loaded or when there's any changes made to the source code,
FEAT will automatically syncronize the database with the source code and checks
whether the concern graph is consistent with the updated database. If not, a
red-X flag
will be added on top of the concern which contains such inconsistencies.
To view inconsistent elements or relations:
- Switch to FEAT Perspective with the Concern Graph View open.
- Right-click on the concern with inconsistency flag.
- In the pop-up menu, choose "inconsistencies".
- The Inconsistency View will show up.
For details on how to understand and repair each type of inconsistencies, please refer to the Inconsistency View.