Skip to content

Don't use Debug.Logs for output results on NotNullFinder #7

Description

@edwardrowe

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:
mockup_notnullviewer_ 4

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions