[field: Serializefield]

Unity Courses Talk
,
#1

There is a third option, instead of using
[SerializeField] private type _myField;
you can use
[field: SerializeField] public type myField {get; private set;}
You gain the option to add a public getter, while keeping the setter private and exposed in the inspector. However, it seems to break the [Header()] tags within unity.
I find it useful for some (certainly not all though) use cases :slight_smile:

9 Likes
#2

This is good to know! Thank you for sharing!

#3

Yup that’s a valid option if you want that field to be read by other classes

1 Like
#4

yes unfortunately, Unity doesn’t show auto-properties yet :stuck_out_tongue:

#5

I’ve almost always taken a page out of the C++ book in this instance and would have a

private int exampleVariable
public int ExampleVariable { get { return exampleVariable; } }

This way we keep the main instance private and un-editable from other scripts but are still able to access it.

1 Like
#6

Yes, that is always a valid way to get the best of both worlds. You can even shorten it a bit to

[SerializeField] private int _i;
public int I => _i;
3 Likes
#7

What do you mean it breaks the header tags? I haven’t been able to see any difference so far between that and serialized field

#8

Unity can serialize auto properties to Inspector with [field: SerializeField] attribute.

#9

[field: SerializeField] for auto properties does not break Header attribute, you must simply add the same target specifier to other attributes including the Header and it’ll work.

   [field: Header("HeaderName")]
   [field: SerializeField] public T Variable { get; private set; }

Privacy & Terms