Refactoring ScriptableObject / Monobehaviour class names about unity-atoms HOT 2 CLOSED

There is an option for something like this for fields where changing the name of a serialized field can result in a loss of the reference/value. In that example the attribute [FormerlySerializedAsAttribute] is available and can help preserve older references. See here for more information on usage.

The problem here though is that its not the reference itself that gets lost, its that the type itself changes when the class is renamed. Unity can't automatically convert from the old to the new type. This isn't likely something that can be solved this way. In general you're much better off settling on a name when first developing.

There are plugins and tools that can make it easier to find broken or missing references though. OdinInspector offers some limited scene validation using their [NonNull] attribute on serialized fields and a custom editor window which allows you to verify that a scene isn't missing any references. My AssetValidator tool here takes this up a notch by allowing you to run validators on your content for the before named functionality as well as a host of others. There are also some widely available menu item scripts that people have iterated on over the years like this that help you to find missing references and such without needing to use a dedicated plugin or tool.

from unity-atoms.

Closing issue due to not being relevant to Unity Atoms.

from unity-atoms.