Auto-generated endpoints from component code
See original GitHub issuegood point via Twitter:
The current docs confused me a bit as a Next.js user by comparing
load
to getServerSideProps/getStaticProps, while it’s more like getInitialProps in the way that it exposes everything to the client.
They currently say this, which isn’t totally accurate:
load
is the SvelteKit equivalent ofgetStaticProps
orgetServerSideProps
in Next.js orasyncData
in Nuxt.js.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Autogenerating Configurations for Components to Confluent ...
Use the following script to autogenerate delta configuration files for Confluent Platform components and clients connecting to Confluent Cloud. These delta ...
Read more >How to automatically generate REST endpoints from a file ...
I built a class that generates code for all the paths via 2 template files and saves the resulting java class in the...
Read more >An Insight into APIMatic's Autogenerated SDKs
APIMatic autogenerates SDKs in multiple languages so developers can consume APIs in their favorite development environment with less code ...
Read more >Component autogeneration - Magnolia CMS Docs
Autogeneration creates components inside an area automatically without editor involvement. Anything you define under the content node will be autogenerated.
Read more >Generate GraphQL Types with Apollo Codegen Tutorial
TypeScript GraphQL Code Generator – Generate GraphQL Types with Apollo Codegen ... Download any GraphQL schema using a GraphQL endpoint ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Will SvelteKit ever consider adding a
getServerSideProps
equivalent then? 🤔Not exactly — firstly there’s a bug (#823), but secondly that will also prevent any interactivity at all on the page, which might coincide with your requirements but often won’t. Partial hydration needs solving at a lower level (i.e. Svelte) if we want it in SvelteKit