@gentbajko/slopify 3.14.1 → 3.14.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
# Slopify 3.14.2
|
|
2
|
+
|
|
3
|
+
Released 9 October 2026.
|
|
4
|
+
|
|
5
|
+
- **New videos get their readable folder too.** A project made after 3.14.0 kept its old folder once it finished, because a few placeholder steps that never run still looked like work waiting. Slopify now sorts a finished project into Upload, Working and History shortly after it's done, as it does for older projects.
|
|
@@ -22,7 +22,10 @@ export function arrangeKeys(db) {
|
|
|
22
22
|
// Whether anything of the project runs or may start: its files stay where they are until then.
|
|
23
23
|
export function projectSettled(db, projectId) {
|
|
24
24
|
const busy = db
|
|
25
|
-
.prepare(`SELECT 1 FROM revision_work WHERE project_id=? AND (state='running' OR (state='pending' AND dispatch_state!='held'
|
|
25
|
+
.prepare(`SELECT 1 FROM revision_work w WHERE w.project_id=? AND (w.state='running' OR (w.state='pending' AND w.dispatch_state!='held'
|
|
26
|
+
-- A deferred "…:future" stand-in stays pending after its real steps have run; the run
|
|
27
|
+
-- leaves it out (rebuild/runtime-store.ts executionStages), so it is not work to wait for.
|
|
28
|
+
AND EXISTS(SELECT 1 FROM revision_work_pieces p WHERE p.work_id=w.id AND p.work_key NOT LIKE '%:future')))
|
|
26
29
|
UNION ALL SELECT 1 FROM stages WHERE project_id=? AND state='running'
|
|
27
30
|
UNION ALL SELECT 1 FROM project_trash WHERE project_id=? LIMIT 1`)
|
|
28
31
|
.get(projectId, projectId, projectId);
|