Errors Visualization

Each Bind<T> Source and Path fields can visualize various errors and ask the user to take action. The errors are not automatically fixed to avoid hiding unwanted side effects from the user, the user should be aware of the errors. Below are some examples of errors the user may encounter:

The gameobject doesn't have a component

The gameobject doesn't have a component

If for example a field in the bind path is not available anymore, the user will be prompted with the error.

Long bind path

Error when field is missing in bind path

There are other errors not listed here, usually the user will have to select the object with issues to see these errors. In a future update, a global validator will provide all errors without requiring users to select problematic objects.