Don't use Debug.Logs for output results on NotNullFinder #7
Description
Debug log clutters the log, and may not be how most people want to deal with their objects. I envision a list view of every monobehavior that is erroring, with a "Select" button that allows them to select the object with the problem. Note it's impossible to select a prefab game object that's 2 children deep.
Currently the information we provide on each error is:
Object Name
- Full object name (including parents)
- Path To Object or Scene
- Field Name for each error
- Monobehaviour name for each error
Here is a mockup for how an item in the list could display:
