mirrors/leptos-book
1
0
Fork 0
mirror of https://github.com/leptos-rs/book.git synced 2025-12-27 10:01:41 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update 10_resources.md (#190)

Browse Source 
corrected typo
This commit is contained in:
ryykdev
2025-04-18 16:23:57 +02:00
committed by GitHub
parent 7e9ce9a9cd
commit acdf261749
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/async/10_resources.md
View File

@@ -4,7 +4,7 @@ Resources are reactive wrappers for asynchronous tasks, which allow you to integ
They effectively allow you to load some async data, and then reactively access it either synchronously or asynchronously. You can `.await` a resource like an ordinary `Future`, and this will track it. But you can also access a resource with `.get()` and other signal access methods, as if a resource were a signal that returns `Some(T)` if it has resolved, and `None` if it’s still pending.
Resources come in two primary flavors: `Resource` and `LocalResource`. If you’re using server-side rendering (which this book will discuss later), you should default to using `Resource`. If you’re using client-side rendering with a `!Send` API (like many of the browser APIs), or if you have are using SSR but have some async task that can only be done on the browser (for example, accessing an async browser API) then you should use `LocalResource`.
Resources come in two primary flavors: `Resource` and `LocalResource`. If you’re using server-side rendering (which this book will discuss later), you should default to using `Resource`. If you’re using client-side rendering with a `!Send` API (like many of the browser APIs), or if you are using SSR but have some async task that can only be done on the browser (for example, accessing an async browser API) then you should use `LocalResource`.
## Local Resources