thatopen-syntax-components

To get a ThatOpen component instance correctly, always use the components.get() singleton pattern from the registry. Direct instantiation causes duplicate, untracked component state, leading to runtime inconsistencies and lifecycle failures.

Implementing Disposable and Updateable lifecycle interfaces correctly requires following strict setup contracts for deferred initialization and ensuring every owned event is properly reset during dispose(). Adhering to these lifecycle contracts prevents memory leaks and invalid state transitions.

Reactive DataMap and DataSet collections cause memory leaks when anonymous event handler references are not properly managed. You must maintain safe Event handler references and execute reset-on-dispose practices to ensure clean teardown and prevent reactive collection update leaks.

You cannot directly instantiate ThatOpen custom components. Doing so is an anti-pattern that bypasses the registry's tracking. You must register custom components and access them via components.get() to maintain valid singleton state and correct lifecycle behavior.

Using ThatOpen components after calling dispose() is an anti-pattern that causes undefined behavior because the component state is destroyed. You must ensure safe teardown by removing event subscriptions and avoiding any component access after the disposal method completes.