How I felt reading an article about the HTML <output> element today, but it is for sure not the first time this has happened.

This helped me paint a better mental picture, although it still makes more sense to me to maintain an awareness of the separation of the server and client
Exposing API routes in frameworks like SvelteKit or Next feels closely-knit enough + nowadays there are a lot of ways to generate types for API's

Had a similar issue with passed bindable state, I was recommended to do this:
setContext("value", ()=>yourState);
So instead of passing the state, you pass a function that returns it. Somehow makes a difference.

How have I never heard of <hgroup> before?

This is the main thing keeping me on Notion, so exciting to see it's getting there 🤩

Alright, somehow I cannot wrap around to how it can infer rest but not key1 and key2, but that's probable a me-problem 😅 The examples you pass are helpful, I guess I just wish it would not be needed to do double bookkeeping.
Thanks anyway for guiding me and I hope you are doing well! 🫶

But at the same time the type does resolve properly, the result is typed as string. Anyway maybe my mind is just stubborn on this one ¯\_(ツ)_/¯

And why would it not know key1, but it would know the restprops?

but if I write key1: key1 as T['key1']` in the return statement, it will resolve it to string. What exactly is the difference?

The internet needs more of this

Ahah thanks 🫶 It just seems like such a basic thing, blows my mind 🙃