Skip to content

Editor

Purpose

Owns editor tooling used by the Prefab Metadata type system.

These systems provide custom inspectors, editing workflows, and authoring utilities used when working with Prefab Metadata assets and type databases.

Owns

  • Metadata custom inspectors
  • Prefab type editing workflows
  • Metadata authoring tools
  • Type database editor integration
  • Metadata editor UX

Does NOT Own

  • Runtime metadata storage
  • Metadata models
  • Metadata filtering
  • Metadata databases
  • Metadata discovery workflows

Allowed Dependencies

Editor may depend on:

  • Metadata
  • Unity Editor APIs
  • ScriptableObject tooling
  • AssetDatabase APIs

Editor systems should avoid owning runtime metadata behaviour.

Notes

Editor tooling exists to improve authoring workflows when working with metadata assets.

Examples include:

  • Prefab type dropdowns
  • Metadata inspectors
  • Type database editing
  • Metadata validation
  • Authoring utilities

These systems are editor-only and are not included in runtime workflows.