A FeatureCell does not start with "whatever was in the constructor." Calling initialize() activates the runtime pipeline, and the value it begins with depends on a resolved decision between a declared default, a previously persisted value, and a deliberate hydrate() factory. Knowing which source wins β and why β is what separates an accidental starting value from an intentional one.
This post walks through what initialize() actually activates, when hydrate() overrides everything else, and how to choose between a static default, Persist behaviors, and an explicit factory when your FeatureCell comes online.
Key takeaway: Initialization is not a direct mutation. Whatever value is selected β hydrated, persisted, or declared β is enqueued as a replaceState operation and processed through the same pipeline as any other update.
Initialization Is a Runtime Boundary
A FeatureCell is not operational the moment it is declared.β¦