Task: Migrate Legacy Svelte Stores to Runes

[stricklandrbls]

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.

[ShilpaNair96]

Hello! Is this still active?

[stricklandrbls]

Hello, @ShilpaNair96! Yes this issue is still open and available.

[ShilpaNair96]

Great! I'd like to work on it please. This would be my first time contributing. I hope that's ok.

[stricklandrbls]

@ShilpaNair96 You're free to take a shot at it. Whenever you feel that it's ready for review go ahead and open a PR.

I would suggest forking the respository into your GitHub profile and creating the PR with the apache/daffodil-vsocde as the base.

Feel free to @ any of us if you feel that you need help or confused about something.

---

I have some implementations complete for this that you can use as a reference. The branch is located here: https://github.com/ctc-oss/daffodil-vscode/tree/1645-task-migrate-legacy-svelte-stores-to-runes.

Also, be sure to add tests for the updated runes you implement. They go in the src/svelte/tests directory and can be ran via yarn test:svelte or through the Test Explorer tab. If you prefer the Test Explorer then I would recommend installing the Vitest extension.

[ShilpaNair96]

Great, thanks! I'll get back to you soon