Why aren't PropertyDrawers called FieldDrawers?

Unity Engine
1

PropertyDrawers, so far as I can tell, don’t work on Properties - they only work with Fields. Why not call them FieldDrawers?

Or is there a way to make them work on properties?

2

Clarify…?

When you write a property drawer, it overwrites the gui for any instance of that class or struct, in whichever components have properties of that type
Nomenclature is meaningless

3

No, it only overwrites the gui for fields (SerializedFields in fact) but not properties, so that’s why calling them FieldDrawers would be more logical.
Nomenclature is not meaningless.

4

But those fields are to control the properties
how else would you set the properties?

5

Properties control access to fields. Not the other way around. Fields don’t need properties.

This seems to be another weird example of UT making little sense.

6

Is propertydrawers sealed?
If not, derive a new subclass called fielddrawer and we can all have no more conversation about this bizarre cover up.

7

PropertyDrawers don’t work with Properties or Fields. They work with Serialized Properties

8

Ooooh, I hadn’t even thought to try that - I’ll give building my own SerializedProperty a shot.