Augmenting Diff View With External Code Properties
Developers use diff view to understand the changes between two versions of code. While diff focuses mainly on textual changes, software itself is not about text. By providing additional information like warnings about possible bugs we can help developers to understand a purpose or identify side effects of the change.
The idea of this project is to integrate already available information about external properties of software (such as code quality critics) into a diff view.
- Obtaining external properties from a non-current version of a software.
- Figuring out how to display the external properties on the changed code.
- Analyzing whether the current model of external properties is suitable for a diff viewer.
- Investigating how the enhanced diff influences developers. E.g. whether the developer that sees that he's about to commit a bad-styled code will improve it.
The project will be done in Pharo. The external properties model Renraku is already used by the default Pharo tools (code browser, inspector, spotter) with Ð° help of the extensions provided by QualityAssistant
If implemented well, the enhanced diff will replace the default diff in core Pharo distribution.
Depending on the tackled challenges, this project can serve for seminars as well as bachelors or master students.