chore: update readme
This commit is contained in:
parent
abe1e9d2d2
commit
49ef3be87a
1 changed files with 11 additions and 1 deletions
12
README.md
12
README.md
|
@ -3,7 +3,17 @@
|
||||||
Utilities for serializing data from server for use in the client.
|
Utilities for serializing data from server for use in the client.
|
||||||
|
|
||||||
1. `Serialize` Astro component takes `id` and `data`
|
1. `Serialize` Astro component takes `id` and `data`
|
||||||
1. `deserialize(id: string): Object` function for use int he client takes an `id` string and returns the `data` as Object
|
1. `deserialize(id: string)` function for use int he client takes an `id` string and returns the `data`
|
||||||
|
|
||||||
|
## What's happening here?
|
||||||
|
|
||||||
|
For simple applications with just a few components, this is a quick pattern to embed serialized information into your HTML. The `Serialize` component will do this for you, currently by using a hidden `textarea` element to hold the string.
|
||||||
|
|
||||||
|
The `deserialize()` function can then parse the value string for use in your client script.
|
||||||
|
|
||||||
|
This is not the best way to do this though. Other frameworks might do this by embedding JSON in your HTML and managing/tracking the IDs for you, but we don't have access to this yet in Astro. You have to manage the IDs yourself and understand the the `deserialize()` function will crawl the whole document.
|
||||||
|
|
||||||
|
There is a pattern given in the Astro docs to use a Custom Element that takes a `data-` prop which properly protects the scope of your component. That is a good pattern to follow for complex applications that don't use UI frameworks.
|
||||||
|
|
||||||
## Installation & Examples
|
## Installation & Examples
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue