- Issue created by @eiriksm
- Status changed to Fixed
5 months ago 7:22pm 12 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.
Currently on violinist.io, there is code scattered around related to finding,. displaying and updating the status of a project (whether it's running, queued and so on).
We probably don't want to add this as a field on the node, since it would be constantly changed in the background, leading to all kinds of potential race conditions and UX problems (like "this content has been changed by another user, please reload")
-
Add a service dealing with storing, fetching, caching, invalidating cache, creating render arrays
-
Only additions
Fixed
1.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.