Skip to content

Commit 7a91a4b

Browse files
author
brucou
committed
chore(README): update
1 parent aa90d00 commit 7a91a4b

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,11 @@
55
- [Motivation](#motivation)
66
- [So what is a component combinator?](#so-what-is-a-component-combinator)
77
- [Examples](#examples)
8-
- [Login gateway](#login-gateway)
8+
- [Separating layout from feature](#separating-layout-from-feature)
99
- [Nested routing](#nested-routing)
10+
- [Login gateway](#login-gateway)
11+
- [Multi-step workflow](#multi-step-workflow)
1012
- [Dynamically changing list of items](#dynamically-changing-list-of-items)
11-
- [Layouting](#layouting)
1213
- [Composing an app from components](#composing-an-app-from-components)
1314
- [Roadmaps](#roadmaps)
1415
- [Roadmap v0.5](#roadmap-v05)
@@ -90,9 +91,9 @@ A component combinator is a **parametrizable** function which... **combines** co
9091
The simplest of those
9192
combinator is `Combine` (for instance `Combine{{...}, [C0, [C1, C2]]}`), whose DOM sink is
9293
the result of merging `Cx` DOM sinks **into** `C0` DOM sink; and whose non-DOM sinks are
93-
the merge of the respective `Cx` non-DOM sink.
94+
the merge of the respective `Cx` non-DOM sink. Here the combining logic is a merge logic.
9495

95-
The principle is deceptively simple. Now let's see some examples of use.
96+
So the general principle is fairly simple and generic. Now let's see some practical examples of use.
9697

9798
# Examples
9899
## Separating layout from feature

0 commit comments

Comments
 (0)