apache/daffodil-vscode

Task: Migrate Legacy Svelte Stores to Runes

Open

#1,645 opened on Mar 26, 2026

View on GitHub
 (7 comments) (0 reactions) (1 assignee)TypeScript (32 forks)auto 404
code qualitydata editorgood first issuetypescript

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

Task: Migrate Svelte Stores to Runes

Description  

There have been some functionality issues observed while implementing current Svelte related issues regarding the legacy Svelte $store usage due to Svelte 5 introducing Runes as a replacement.

This task is for migrating all of the legacy stores to utilize the rune development structure.

It had previously been determined that if a developer was working an issue that "touched" a svelte file then they should go ahead and perform the required migration. This is no longer a viable solution due to the numerous derived stores that currently exist. Legacy stores written as $derived do not perform well when the variable's dependent derivation has been changed to a Svelte 5 rune.

Acceptance Criteria  

  • No legacy svelte stores in use.
  • Functionality remains in tact.

Steps / Subtasks

Ideally, the index.ts file that contains the UI global svelte stores should be worked first.

Contributor guide

Research direction
Start by locating all legacy store files in the project, typically in an index.ts file under UI global stores. Then systematically convert each store from writable/derived using $ to runes (e.g., $state, $derived). Ensure dependency tracking works correctly, especially for derived stores that depend on other runes. Test each conversion by running the extension and checking functionality.
Tech stack
typescriptsvelte
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptSvelteGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45