Use code weaving

This will solve our API accessibility issue when using UnityEvent’s inspector to wire things up.

if private field X has [Tooltip] attribute 
then create public Property X
if found method ConfigureX
then add ConfigureX to end of Property X.setter
and create OnValidate add ConfigureX to OnValidate
if Property is descendant of `UnityEngine.Object`
then add `ClearX()` method which sets field to `Default(T)`
if Property is a collection
then add `ClearX()` method which calls x.Clear()
If Property is "sub class"
then add `ClearX()` method which sets sub class to `Default("sub class")`

ConfigureX here can optionally return T to change the value we set in the property setter. This allows clamping values for example.

[thestonefox]

I just remembered. We need to make sure anything that extends UnityEngine.Object needs to get a ClearMyProperty() method that sets it to null because you can’t clear then via the UnityEvent otherwise.

Or we could make it easier and everything gets a

public virtual void ClearMyProperty() {
  MyProperty = default(MyProperty.GetType());
}

[bddckr]

Hmm. I’d love to support things like that (and vectors!) that aren’t supported by Unity as constants there.

Such a method doesn’t help us, though? Users don’t really know the enum values in advance and for bitfields it would be even harder for them.

Besides us having to support all backing types:

The approved types for an enum are byte, sbyte, short, ushort, int, uint, long, or ulong.