mirror of
https://github.com/cupcakearmy/svelte-cloudinary.git
synced 2024-12-22 16:06:25 +00:00
Update README.md
This commit is contained in:
parent
1e987f84b9
commit
1e14e44a64
16
README.md
16
README.md
@ -47,7 +47,21 @@ yarn add svelte-cloudinary
|
|||||||
This will formulate the Cloudinary url and insert it into the `img.src` property.
|
This will formulate the Cloudinary url and insert it into the `img.src` property.
|
||||||
Also it will resize to the `img` object itself because we set `bind: true`.
|
Also it will resize to the `img` object itself because we set `bind: true`.
|
||||||
|
|
||||||
## Key Concepts
|
## 🤔 Why an [action](https://svelte.dev/docs#use_action) and not component?
|
||||||
|
|
||||||
|
Well components are great of course, but when we only need to set a `src` tags we can leverage the upsides of a svelte [action](https://svelte.dev/docs#use_action)
|
||||||
|
|
||||||
|
What are benefits?
|
||||||
|
|
||||||
|
- Native styling (Svelte for now does not allow easy styling of child components
|
||||||
|
- Lightweight
|
||||||
|
- Reusable and composable
|
||||||
|
|
||||||
|
Downsides:
|
||||||
|
|
||||||
|
- The src will not be set serverside, so also not in the initial server response. Which I believe is not that bad though for images.
|
||||||
|
|
||||||
|
## 🤓 Key Concepts
|
||||||
|
|
||||||
### `step`
|
### `step`
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user