Problem/Motivation
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")
Steps to reproduce
-
Proposed resolution
Add a service dealing with storing, fetching, caching, invalidating cache, creating render arrays
Remaining tasks
- Write the service
- Write some tests
- Commit
User interface changes
-
API changes
Only additions
Data model changes
Comments
Comment #2
eiriksmComment #5
eiriksm