Skip to content

Commit df442bb

Browse files
committed
#7168 polishing
1 parent c427b71 commit df442bb

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

learn/blog/v10-deep-dive-vdom-revolution.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ class MyComponent extends Container {
6666
items : [{module: Button, text: 'Button 1'}]
6767
}, {
6868
ntype: 'component',
69-
html : 'Content Area'
69+
text : 'Content Area'
7070
}]
7171
}
7272
}
@@ -76,6 +76,9 @@ With this method, you are not thinking about HTML, divs, or even the VDOM. You a
7676
of its logical components and their relationships. This is the classic approach for building robust, enterprise-scale
7777
applications where separation of concerns and maintainability are paramount.
7878

79+
From a Micro-Frontends perspective: The **named** configs here are the contract (API) available from the outside.
80+
Any run-time value change is reactive and will update the UI.
81+
7982
### 2. The Functional Way: Direct VDOM Control with JSON Blueprints
8083

8184
For functional components, or when you need to dynamically generate UI structures, you can drop down a level of

0 commit comments

Comments
 (0)