Marek Dědič

Hmm, that looks like it is the correct format :/ Can you send me a link to [email protected]?

Hi, thanks for the report, I have a few questions which should help me to better pinpoint the issue: 1. Do I understand it correctly that the issue happens after...

Heleta původí má poslední commit před 4 měsíci, to mi nepřijde opuštěné... Ale release už nemá dlouho. Vzhledem k citlivosti toho API bych byl s forky opatrný.

V tom případě bych zvážil vlastní fork, klidně založený na nějakém jiném, ale byl bych dost opatrný u knihovny přistupující k bankovnímu API. Nebo nějaký systém review té knihovny...

Hi, sorry if this is unfinished and you're planning to add this, but atm, this ignores https://github.com/sveltejs/eslint-plugin-svelte/issues/1052#issuecomment-2630480779

I still have to disagree - the rule now has a clear false positive that can be detected by its implementation, but just isn't. And I'm sorry, but yeah, you...

Of course, see https://github.com/sveltejs/eslint-plugin-svelte/issues/1052#issuecomment-2630480779 for a simple example or [here](https://github.com/scout-handbook/handbook-web-admin/blob/2bd402626049e75af7a6d7b9c0b1f7a75b6bff2e/src/lib/resources/fields.svelte.ts#L11-L25) for a real-world example (this one is in `$derived`, but the same semantics apply)

Thanks :) I don't even think it needs to be an option - if a `$state(SvelteMap)` is reassigned, the `$state` is always necessary...

Hmm, you are absolutely right that the code snippet is incorrect, thanks, I din't realize that! I am thinking if this isn't a separate issue, though - the anti-pattern here...

Hi, typescript-eslint released v8 yesterday with full eslint v9 support, is there something to be done to move this forward? Thanks!