Skip to content

feat(filinq): build flow-operations - #2062

Merged
rubenvdlinde merged 2 commits into
developmentfrom
quality/build-flow-operations
Nov 14, 2026
Merged

rubenvdlinde merged 2 commits into
developmentfrom
quality/build-flow-operations

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Tasks done (partial build)

  • 1.1 flowOperationRun in lib/Settings/filinq_register.json (register 8.52.0):
    • the twelve fields of design D6, with the operation and status enums;
    • x-openregister-lifecycle starting at queued: start, succeed, fail, and skip from queued;
    • x-openregister-archival with the P1Y retention placeholder that task 1.3 must replace before apply;
    • flowOperationFailed in the verified notification dialect (scheduled + status: failed) to ownerUserId only.
    • Writes are server-only: create/update nobody, delete admin. Only the background job records a run, so a log cannot claim a run that did not happen. The reason is in docs/authorization-decisions.md, as the authorization coverage test requires.
  • 1.2 The two runs from design.md plus a skipped own_output run, in lib/Settings/filinq_mock_register.json. The demo-data rule asks three per schema, and the mock register is where demo data lives, so no fake run is installed on a real instance.

Tasks left, and why

  • 2.1-2.5 (the four Flow operations, their registration, the queued job, the loop guard and the service wiring) are one piece: registering operations before the job that runs them would let people save Flow rules that never act. 3.1-3.3, 4.1-4.5 follow them. 1.3 waits on a selectielijst decision. 4.2 and the screenshots are live work.

Tests added

  • tests/unit/Settings/FlowOperationRunSchemaTest.php, 7 tests: the register lists the schema; the fields and enums; server-only writes; the lifecycle moves and terminal states; the retention placeholder; the owner-only failure notice; and the three demo runs (none in the production register).

Suite before/after

  • PHP unit: 6443 to 6450 tests, 0 failures both times (6 skipped as before).

Generated by Claude Code

Add the flowOperationRun schema, the processing log of a Filinq operation
a Nextcloud Flow rule starts: its fields, lifecycle, retention placeholder,
failure notice to the file owner and server-only writes, with three demo
runs in the mock register (tasks 1.1, 1.2).

Assisted-by: ClaudeCode:claude-opus-5-5
Register: keeps development's documentReview and waarmerk schemas and this
branch's flowOperationRun schema; version 8.54.0 since both sides bumped
from 8.51.0. Mock register keeps both sides' demo objects.

Assisted-by: ClaudeCode:claude-opus-5-5
@rubenvdlinde
rubenvdlinde merged commit e0a8c4d into development Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant