@@ -4,12 +4,12 @@ Roadmap
4
4
2021-Q2
5
5
-------
6
6
7
- Element and Component Identity:
7
+ ** Element and Component Identity ** :
8
8
At the moment, whenever a particular branch of a layout is updated, all the state
9
9
(i.e. hooks and event handlers) that live within that branch are thrown away and
10
10
reconstructed. Given IDOM's current implementation for
11
11
:class: `~idom.core.layout.Layout ` this is unavoidable. To resolve this issue, we
12
- need to add a concept of `"keys" <https://reactjs.org/docs/lists-and-keys.html> `
12
+ need to add a concept of `"keys" <https://reactjs.org/docs/lists-and-keys.html >`__
13
13
which can be used to indicate the identity of an element within the layout
14
14
structure. For example, if you have a list of elements that get re-ordered when a
15
15
button is pressed, their state should be preserved, and reassigned to their new
@@ -29,7 +29,7 @@ Element and Component Identity:
29
29
- https://github.com/idom-team/idom/issues/330
30
30
- https://github.com/idom-team/idom/issues/19
31
31
32
- Reconsider Custom Component Interface:
32
+ ** Reconsider Custom Component Interface ** :
33
33
One problem that's come up several times while implementing alternate client
34
34
solutions with React is that custom components must use the same React instances
35
35
as the client. This is problematic for developers of these custom components because
0 commit comments