Skip to content
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.

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

refactor: Updated all Svelte fetch data examples to use #await block. #246

Closed
wants to merge 1 commit into from

Conversation

kotikkir9
Copy link

While reading 'fetch data' examples, I noticed that the current Svelte snippets do not use the #await block, which provides native Svelte functionality for dealing with promises inside the markup. My PR behaves exactly the same as before; it just makes the code simpler and smaller, using native Svelte functionality.

… #await block, which is meant to work with promises. It behaves exactly the same as before, but results in much less code.
@matschik
Copy link
Owner

It would work well with await block but when comparing frameworks, comparing await block with the other implementations can be harder. We already got some proposals to use await block but making easy to compare it more important for the purpose Component Party.

@Thiagolino8
Copy link

Comparing await block with the other implementations can be harder

Why isn't this the case with solid-js, which is using its own API to handle promises?

Making easy to compare it more important for the purpose Component Party

From what I understood, the purpose of component party was to show the differences between frameworks. If the specific capabilities of the frameworks aren't used, it ends up being a tutorial on how to use vanilla js in frameworks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants