Skip to content

advent of svelte day 2 #909

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 2, 2024
Merged

advent of svelte day 2 #909

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6002383
advent of svelte day 2
Rich-Harris Dec 2, 2024
2757e68
Merge branch 'main' into each-without-as
Rich-Harris Dec 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions apps/svelte.dev/content/blog/2024-12-01-advent-of-svelte.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,17 @@ Follow [@svelte.dev](https://bsky.app/profile/svelte.dev) and [@sveltesociety.de

## Day 1: Error boundaries

This is a long-awaited and much-requested feature, that allows you to isolate and recover from errors that occur during rendering. See the [docs](/docs/svelte/svelte-boundary) and [tutorial](/tutorial/svelte/svelte-boundary) for more.
This is a long-awaited and much-requested feature, that allows you to isolate and recover from errors that occur during rendering.

## Day 2
- [docs](/docs/svelte/svelte-boundary)
- [tutorial](/tutorial/svelte/svelte-boundary)

Coming soon!
## Day 2: `each` without `as`

If you just want to render something in an `{#each ...}` block _n_ times, and don't care about the value, you can now omit the `as` part.

- [docs](/docs/svelte/each#Each-blocks-without-an-item)
- [demo](/playground/untitled#H4sIAAAAAAAAE3WR0W7CMAxFf8XKNAk0WsSeUEaRpn3Guoc0MbQiJFHiMlDVf18SOrZJ48259_jaVgZmxBEZZ28thgCNFV6xBdt1GgPj7wOji0t2EqI-wa_OleGEmpLWiID_6dIaQkMxhm1UdwKpRQhVzWSaVORJNdvWpqbhAYVsYQCNZk8thzWMC_DCHMZk3wPSThNQ088I3mghD9UwSwHwlLE5PMIzVFUFq3G7WUZ2OyUvU3JOuZU332wCXTRmtPy1NgzXZtUFp8WFw9536uWqpbIgPEaDsJBW90cTOHh0KGi2XsBq5-cT6-3nPauxXqHnsHJnCFZ3CvJVkyuCQ0mFF9TZyCQ162WGvteLKfG197Y3iv_pz_fmS68Hxt8iPBPj5HscP8YvCNX7uhYCAAA=)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be a saved id with a title so we can edit it if needed or do we want to update the url here to not have a separate source of truth for the example in a DB somewhere?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not exactly. my plan is to add some syntax for auto-generating these from docs, but that's a separate chunk of work


## Day 3

Expand Down