Hofer Ivan

> Thank you for the detailed thoughts. One thing I'm not sure about yet is if we should prevent people from setting other style props besides the ones that are...

Ah right. So this feature would need a syntax for defining this for TypeScript users and another syntax for defining it via JSDoc comments. And I think this then should...

@dummdidumm I think putting it into the `$$Props` interface is a bad idea. These aren't really props you have (or should have) access inside the `script` tag. Another aspect is...

@Monkatraz good point! Restricting inputs via template strings is a bad idea.

@WilHall you could use the experimental `$$Props` feature gain back typesafety: https://github.com/ivanhofer/sveltekit-typescript-showcase/blob/main/src/01-props/06-%24%24Props/Component.svelte

Sorry, I thought this is a general issue since I never saw it working. I tried to create a fresh repo but cannot reproduce it there. Then I have deleted...

Yes I was also assuming that this would be a breaking change. Not sure if I understood it correctly but the language tools could "patch" the types without the Svelte-typings...

I just have installed the [`SomewhatStationery.some-sass`](https://marketplace.visualstudio.com/items?itemName=SomewhatStationery.some-sass) extension and it looks promising

Having a similar problem: ```svelte import List from '$components/forms/List.svelte' type Item = { key: string; value: string } export let items: Item[] {#if items[index]} {/if} ``` I would expect that:...

> Thanks for the review! I wasn't expecting a review of the code (although I greatly appreciate it), more of the general idea and thoughts on the questions I mentioned...