Cannot use Task in class outside of component.

[christophsanz]

Describe the bug

I am trying to use a task in class, but i always get lifecycle_outside_component onDestroy(...) can only be used during component initialisation.

Is this a limitation of sheepdog or should i be able to use it outside of a component?

Reproduction

• create SomeClass.svelte.ts file
• add a task as a member to the class
• instantiate and export the class from the same file
• error appears

Severity

blocking all usage of Sheepdog

Package name

svelte

[paoloricciuti]

We automatically tie the task to the component so, yes, it has to be initialized in a component. You can technically use the vanilla version if you want to use it in TS files too. Another thing you could do is to create a function using the transform function and then initialise the task inside a component. Do you have a small example of what you are trying to achieve?

[christophsanz]

Thank you for your quick response!

I have remote data, that i need in multiple components across the app. So i wanted to contain all this logic into a single class that i can just import wherever i want and access the data from there.
This would reduce the amount of server requests since i can reuse the existing data everywhere, and refresh and modify the data everywhere with instant updates across the entire app.

I found a solution, but it kinda annoying. I create the class instance in my App.svelte component, and do a setContext with this instance so i can retrieve it everywhere. Just importing it wherever i need would be lot neater :).

Is there a documentation for the vanilla version?

[paoloricciuti]

There is: https://sheepdog.run/vanilla/getting-started/what-is-it/

I see the issue...I would say creating a context in the root and pass that down is generally better in svelte, this way you will have one class for each request independently...with global modules there's more risk of leaking between request.

However if you don't care about that I wonder if we should add an option to not tie the task to a component at all for those situations...I'll talk with the team. Let's keep this issue open as a Feature Request 😊

[christophsanz]

Awesome, fingers crossed 🤞🏻

Yeah its not a Sveltekit App (unfortunately) so leaking is not an issue for me.

Thanks Paolo!