Analyzer codes.
CodeScenes ships a Roslyn analyzer, so these appear in your IDE as you type rather than after a build.
CodeScenes.Shape
The builder file must stay a flat sequence of builder calls, because the plugin reads the source rather than running it. These are compile errors.
SB1001Error
Build body must be a flat sequence of builder calls
SB1002Error
Unrecognized builder call
SB1003Error
Component closure must contain only .Set(...), .OnClick(...) or .OnEvent(...) calls
CodeScenes.Nudge
The call works, but a typed form exists that the compiler can check for you.
SB1101Info
Use the typed .Set(...) form
Use the typed form `.Set(x => x.member, …)` — the compiler checks the member and its type.
SB1102Info
Use the typed prefab reference
Use `Instance(Prefabs.X)` (spec 25) — a stale/typo'd prefab path then fails to compile.
SB1103Info
Use the typed .On(...) selector
Use the typed selector `.On(sel => sel.A.B, …)` (spec 24/25).
SB1105Warning
Use the typed Layers catalog
Use `Layers.<name>` — a typo'd/invalid layer then fails to compile.
SB1106Info
Use the typed Set<T> overload
Use `Set<T>(x => x.member, value)` — the compiler catches value-type mismatches.
CodeScenes.UnityEvent
Persistent listener wiring that Unity would silently drop at runtime.
SB1201Error
UnityEvent listener signature mismatch
Method `{0}` does not match `{1}`'s signature; expected `{2}`.
SB1202Warning
UnityEvent listener target not eligible
Persistent-listener targets must be public instance/static methods matching the event.
CodeScenes.Spatial
SB1203Warning
Two position drivers claim the same axis
Two position drivers on this node claim the same axis; they will fight at runtime. Give them different axes, share one orientation reference, or remove one.