Skip to content

Commit

Permalink
Docs: Update README.md (#25)
Browse files Browse the repository at this point in the history
Fix a broken link to documentation in Laminar repository
  • Loading branch information
reid-spencer authored Dec 10, 2024
1 parent 26e960b commit 80db5fb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ val app: Div = div(
)
```

This is essentially a specialized version of the Airstream's [`split` operator](https://github.com/raquo/Laminar/blob/master/docs/Documentation.md#performant-children-rendering--split). The big idea is the same: provide a helper that lets you provide an efficient `Signal[A] => HtmlElement` instead of the inefficient `Signal[A] => Signal[HtmlElement]`. The difference is that the split operator groups together models by key, **which is a value**, whereas SplitRender groups together models by **subtype** and refines them to a subtype much like a `currentPageSignal.collect { case p: UserPage => p }` would if `collect` method existed on Signals.
This is essentially a specialized version of the Airstream's [`split` operator](https://github.com/raquo/Laminar/blob/master/website/docs/documentation.md#performant-children-rendering--split). The big idea is the same: provide a helper that lets you provide an efficient `Signal[A] => HtmlElement` instead of the inefficient `Signal[A] => Signal[HtmlElement]`. The difference is that the split operator groups together models by key, **which is a value**, whereas SplitRender groups together models by **subtype** and refines them to a subtype much like a `currentPageSignal.collect { case p: UserPage => p }` would if `collect` method existed on Signals.

You should read the linked `split` docs to understand the general splitting pattern, as I will only cover this specialized case very lightly.

Expand Down

0 comments on commit 80db5fb

Please sign in to comment.