public sealed class HotReloadStateAttributeMarks a component member whose value should survive being replaced.
No guide page documents this yet — the page shows what the code says about itself.
As a annotation
- Valid on
- Property, Field
Remarks
⚠ This is not for the common case, and saying which case it is for matters. Re-running a component's Build keeps the component object, so its fields — its signals above all — survive by construction and need no attribute. What does not survive is a replacement: an edit .NET calls rude, a type that has to be recreated, a reload that constructs a fresh instance. Then the new object starts from its own field initialisers, and this says what to carry over.
Carried by name and by name only. Two instances of two versions of a type share nothing else — not a field slot, not a token, not an order — and matching on anything more clever would move a value onto whatever happened to be in the same position.
Used by (2)
- CarryingVixen.Ui.HotReload.Tests
- HotReloadHostVixen.Ui.HotReload