Skip to content

fix(e2e): let each captured flow file under its own category - #246

Merged
haribo merged 1 commit into
developfrom
fix/245-a-case-files-under-its-own-category
Sep 11, 2026
Merged

fix(e2e): let each captured flow file under its own category#246
haribo merged 1 commit into
developfrom
fix/245-a-case-files-under-its-own-category

Conversation

@haribo

@haribo haribo commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • judging a capture filed under account on production: push.ts hardcoded the category (let each captured flow file under its own category #245 — the YAGNI deferral recorded on capture the dead sign-in link as evidence #241 met its counter-example one flow later)
  • The category is now named by each flow: account for the sign-in family, review for the carousel; caseFor keeps finding existing cases by title and never re-categorises them
  • The production case was moved into a review root category by hand (PATCH /cases/{id}), verified

Test plan

  • Suite with OZALID_PUSH_SELF=1: 66 passed — the carousel case files under review on a fresh instance
  • fe-check

Evidence tooling only, no release needed.

Closes #245

@haribo
haribo merged commit 6ae3e16 into develop Sep 11, 2026
3 checks passed
@haribo
haribo deleted the fix/245-a-case-files-under-its-own-category branch September 11, 2026 12:41
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.

let each captured flow file under its own category

1 participant