As a quick TL;DR, for repositories that have multiple independent included builds that each have the doctor plugin applied to them, scanning the prescriptions at the end of the console output can be confusing. I'd like some clarity on which project that the plugin is prescribing changes/fixes for.
I rely on the project's display name here, which should almost always be defined. We can use a path instead, but it may not be as readable for some users.
The motivation behind this is contained in a github issue
As a quick TL;DR, for repositories that have multiple independent included builds that each have the doctor plugin applied to them, scanning the prescriptions at the end of the console output can be confusing. I'd like some clarity on which project that the plugin is prescribing changes/fixes for.
I rely on the project's display name here, which should almost always be defined. We can use a path instead, but it may not be as readable for some users.