Kevin Åberg Kultalahti

@sw-yx I think we really need the core maintainers to weigh in on this. There's no point in building something until then, imo :/

I like this a lot! I'd definitely opt for a more separated thing, **not** allowing `forward:use:internalAction`. Better to have it separate to make it clear what is going on IMO.

Just re-read the part on `Additional Proposal - foward effects and singular event forwarding`. This is trivial to get around at the moment for actions: ``. The same can be...

> I really like forwarding specific events and actions (maybe transitions and animations too?) with `forward:on:event` & `forward:use:action`. Should definitely make it in. `forward:on:event` is not needed, you can already...

> I don't think we need any extra syntax for exposing transitions/actions. You can expose that through props alreay, which is top-down, and introducing a `forward`-syntax for that, which would...

I like this, I also think the syntax looks good!

> When I have time I think I will start working on making this new feature, but I'm not very familiar with the svelte source code so it may take...

This is definitely something we need. I'm open to any of the solutions but it does sound like GraphQL API is the way to go. Does it make sense to...

Yeah I'm not sure, could be a top level category as well 🤔 I'm open to pretty much everything here I think.

I think we could definitely use some kind of GitHub action that runs every week or so that re-deploys the website. I'd like to keep the staging branch, it's a...