Visual distinction between reactive and non-reactive Maps/Sets in editor
hanszoons opened this issue · 1 comments
hanszoons commented
Description
It’s too easy to forget that you need to make Sets and Maps reactive by importing them from svelte/reactivity. I’ve lost MANY hours debugging because an import was 'silently' missing: for example, moving a function that uses Map and Set from a file with reactive imports to one without.
Same goes for when you use libraries or server endpoints that return native Maps and Sets. It’s easy to forget that these are not reactive maps.
Proposed solution
Find a way to perhaps visually distinguish between reactive and non-reactive Maps/Sets (and related) in the editor.
Alternatives
Warn/indicate when non-reactive Maps and Sets are used or mixed with reative.
Additional Information, eg. Screenshots
No response