You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A first-class type picker for [SerializeReference] managed-reference fields, built on the package's existing [TypeSelector]. It replaces Unity's bare managed-reference UI — and the need for a third-party subclass-dropdown plugin — with a hierarchical picker plus full integrity tooling.
Why
Pain today
What this gives
Unity's default [SerializeReference] UI has no type picker
Hierarchical dropdown with search, categories, favorites & recents
Teams pull in a third-party plugin (SerializeReferenceDropdown) just to get a dropdown
First-party, zero extra dependencies — already in the package via [TypeSelector]
Missing / renamed types silently break assets, with no recovery
Detect + repair straight from YAML, at any depth, with ranked Smart Fix
YAML-based missing-type detection (works around UUM-129100); inline Fix at any depth; saved assets, Prefab Mode, saved scenes; Smart Fix; Make Unique for aliases
Its StarterKit also depends on the external com.alexeytaranov.serializereferencedropdown (pinned 1.2.7, repo AlexeyTaranov/SerializeReferenceDropdown), used only for the [SerializeReferenceDropdown] attribute — across ~76 sites (binders, converters, commands).
Once [TypeSelector] covers [SerializeReference] (this issue), MVVM can drop that external dependency and migrate [SerializeReferenceDropdown] → [TypeSelector], consolidating on one first-party tool and gaining repair / graph / generics / favorites for free.
→ Aspid.MVVM becomes the first internal consumer that validates this selector in a large real codebase.
A first-class type picker for
[SerializeReference]managed-reference fields, built on the package's existing[TypeSelector]. It replaces Unity's bare managed-reference UI — and the need for a third-party subclass-dropdown plugin — with a hierarchical picker plus full integrity tooling.Why
[SerializeReference]UI has no type pickerSerializeReferenceDropdown) just to get a dropdown[TypeSelector]Goal: the best-in-market SerializeReference selector, owned end-to-end inside Aspid.
Scope
[TypeSelector]on single / array /List<T>[SerializeReference]fields; pick → instantiate,<None>→ clear, nested props inline; candidates narrowable withtypeof(...)Modifier<T>) — args inferred or picked with constraints[TypeSelectorItem](name / category / tooltip / icon / order); favorites & recents; collapsible groups + searchsr:Quick Search; delete-script guard; proactive breakage notification; build/CI gate;[SerializeReferenceRequired]; Project SettingsConnection to Aspid.MVVM
This is the concrete motivation, not a hypothetical:
tech.aspid.fasttools, since MVVM PR Restructure READMEs, switch demos to GIFs, refresh samples #26).com.alexeytaranov.serializereferencedropdown(pinned1.2.7, repoAlexeyTaranov/SerializeReferenceDropdown), used only for the[SerializeReferenceDropdown]attribute — across ~76 sites (binders, converters, commands).[TypeSelector]covers[SerializeReference](this issue), MVVM can drop that external dependency and migrate[SerializeReferenceDropdown]→[TypeSelector], consolidating on one first-party tool and gaining repair / graph / generics / favorites for free.→ Aspid.MVVM becomes the first internal consumer that validates this selector in a large real codebase.
Tracking on the MVVM side: VPDPersonal/Aspid.MVVM#123.
Status
Implemented by #49 (open).