Skip to content

Commit a29aa64

Browse files
committed
Docs: Clarify distinction between Non-Reactive Configs and Class Fields in Neo.core.Base #7870
1 parent ea3af23 commit a29aa64

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

src/core/Base.mjs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,12 @@ class Base {
7878
* by using the `Neo.overwrites` mechanism, which modifies these prototype values at
7979
* load time.
8080
*
81+
* **vs. Class Fields:**
82+
* Use a non-reactive config when you want the property to be eligible for the `Neo.overwrites`
83+
* mechanism. This allows external code (like themes or application-level overrides) to change
84+
* the default value for the class, which then propagates to all subclasses and instances
85+
* globally. Use standard class fields for internal state that should not be globally reconfigured.
86+
*
8187
* @returns {Object} config
8288
*/
8389
static config = {

0 commit comments

Comments
 (0)