The Reactivity.md guide currently states that Tier 1 (Push-Based Reactivity) is powered by the core.Config system. This is historically inaccurate and conceptually confusing. Tier 1 is powered by the dynamically generated getters and setters created during Neo.setupClass.
The core.Config system, introduced in v10, actually serves as the bridge between the two tiers. Because every reactive config is now internally backed by a core.Config instance, the EffectManager (Tier 2) can observe ANY reactive instance config natively, as well as standalone custom core.Config instances.
This update rewrites the Tier 1 introduction for accuracy and updates the "Synergy" section to explicitly detail how core.Config enables this cross-tier observation, heavily leveraging Neo.state.Provider and createHierarchicalDataProxy as the primary example of this architecture.
The
Reactivity.mdguide currently states that Tier 1 (Push-Based Reactivity) is powered by thecore.Configsystem. This is historically inaccurate and conceptually confusing. Tier 1 is powered by the dynamically generated getters and setters created duringNeo.setupClass.The
core.Configsystem, introduced in v10, actually serves as the bridge between the two tiers. Because every reactive config is now internally backed by acore.Configinstance, theEffectManager(Tier 2) can observe ANY reactive instance config natively, as well as standalone customcore.Configinstances.This update rewrites the Tier 1 introduction for accuracy and updates the "Synergy" section to explicitly detail how
core.Configenables this cross-tier observation, heavily leveragingNeo.state.ProviderandcreateHierarchicalDataProxyas the primary example of this architecture.