Package strange.extensions.mediation.api

Classes
interface	IMediationBinder
	Interface for the Binder which maps Views to Mediators. More...
interface	IMediationBinding
	Interface for MediationBindings. More...
interface	IMediator
	Look at strange.extensions.mediation.api.IMediationBinder, where I explain the purpose of Mediation in detail. More...
class	IView
	Monobehaviours must implement this interface in order to be injectable. More...

Enumerations
enum	MediationEvent { MediationEvent.AWAKE, MediationEvent.DESTROYED, MediationEvent.ENABLED, MediationEvent.DISABLED }
enum	MediationExceptionType {   MediationExceptionType.NO_CONTEXT, MediationExceptionType.MEDIATOR_VIEW_STACK_OVERFLOW, MediationExceptionType.NULL_MEDIATOR, IMPLICIT_BINDING_MEDIATOR_TYPE_IS_NULL,   IMPLICIT_BINDING_VIEW_TYPE_IS_NULL }

Enumeration Type Documentation

enum strange.extensions.mediation.api.MediationEvent

Enumerator
AWAKE	The View is Awake.
DESTROYED	The View is about to be Destroyed.
ENABLED	The View is being Enabled.
DISABLED	The View is being Disabled.

enum strange.extensions.mediation.api.MediationExceptionType

Enumerator
NO_CONTEXT	Exception raised when a View can't locate a Context. Views contact the Context by "bubbling" their existence up the display chain (recursively using transform.parent). If a View reaches the top of that chain without locating a Context, it will raise this Exception to warn you. Note: to avoid infinite looping, there is a bubbling limit of 100 layers. If your View needs to be more than 100 transforms deep, that might signal a design problem.
MEDIATOR_VIEW_STACK_OVERFLOW	Exception raised when a View is mapped to itself. If a View is accidentally mapped to itself, the result will be an infinite loop of Mediation creation.
NULL_MEDIATOR	Exception raised when AddComponent results in a null Mediator. This probably means that the mapped "mediator" wasn't a MonoBehaviour.