mirror of https://github.com/status-im/reagent.git
Fix documentation links
This commit is contained in:
parent
bd8603dce8
commit
c828e22b5f
|
@ -13,7 +13,7 @@ Best to nip these slippery slopes in the bud (and, equally, to never use mixed m
|
|||
|
||||
## Components
|
||||
|
||||
In an earlier tutorial [[Creating Reagent Components]] , we saw that the centerpiece of a Reagent/React component is a **renderer** function. Optionally, a Component might have other lifecycle functions, but a renderer function is central and mandatory.
|
||||
In an earlier tutorial [Creating Reagent Components](CreatingReagentComponents.md), we saw that the centerpiece of a Reagent/React component is a **renderer** function. Optionally, a Component might have other lifecycle functions, but a renderer function is central and mandatory.
|
||||
|
||||
We also saw that Reagent render functions turn data into hiccup: `data -> hiccup`
|
||||
|
||||
|
@ -152,7 +152,7 @@ Armed with a bit more knowledge, we'll revisit this subject at the end of the ne
|
|||
|
||||
## A Further, Significant "Why"
|
||||
|
||||
In the examples above, we've explored [Form-1 components](https://github.com/Day8/re-frame/wiki/Creating%20Reagent%20Components) - the simplest kind - and we've seen we have some choice regarding use of `()` or `[]`. Eventually, I claim that `[]` is much preferred, but you can get away with `()`, up to a point.
|
||||
In the examples above, we've explored [Form-1 components](CreatingReagentComponents.md#form-1-a-simple-function) - the simplest kind - and we've seen we have some choice regarding use of `()` or `[]`. Eventually, I claim that `[]` is much preferred, but you can get away with `()`, up to a point.
|
||||
|
||||
**But** ... the moment you start using Form-2 or Form-3 components, you absolutely must be using `[]`. No choice. Using `()` just won't work at all. Given the explanations above, I'm hoping you can work out why. Either that or just shrug and use `[]` forever more.
|
||||
|
||||
|
|
Loading…
Reference in New Issue