adiGuba

@Thiagolino8 : personally I like the idea of having the choice between snake_case or camelCase. But if multiple casings will cause problems with intellisense, we can restrict to one (but...

Personally, I would go for all 3 syntaxes, in order to be compatible with any other external API There no conflicts between them, and the style attributes can accept multiples...

It's just that Svelte offers a simple and effective transition module, but which is restricted to `{#if}`/`{#each}`. So we have all the basic, except that we cannot invoke it directly...

> Unless my analysis is off (which is entirely possible), [`svelte2tsx`](https://github.com/sveltejs/language-tools/tree/master/packages/svelte2tsx) would need to be adjusted to transform `$derived` into the form `some_function(() => )`. I have never touched that...

Hello, Another alternative would be to use **unsafe-hashes**, since all inserted codes have the same content : `this.__e=event` => This works : ```js csp: { mode: "auto", directives: { "script-src":...

I don't thinks it's the PR 17266. It very simple and only add a warning on props. It do no change the generated code.

I may be saying something stupid, but why not also replace the reactive `$.get(name) ?? ""` by something like `$.txt(name)` ? With `txt()` defined like this : ```js function txt(signal)...

Another stupid idea : why not using a tagged template for cleaning `null/undefined` ```diff -$.template_effect(() => $.set_text(text, `${i ?? ""}: ${l ?? ""}`)); +$.template_effect(() => $.set_text(text, $.TXT`${i}: ${l}`)); ``` With...

The debug message is also useless since it only displays 'Proxy'... I think it could be fixed easily by using `$.snapshot()` on all the variables in console.log(). It may be...

In **Svelte 4** `@debug` already fire on any changes within the object... but of course it's limited by the Svelte 4 model and source-analysis. Example : https://svelte.dev/repl/8248f009ac7946f9840fa6103f7d2568?version=4.2.19 This is a...