From 4f97c00860d3b48ea1b7462bc8d74fe6b0438122 Mon Sep 17 00:00:00 2001 From: Samir Boulahtit Date: Sun, 21 Dec 2025 21:03:36 +0100 Subject: [PATCH] fix: correct YAML syntax in background_tasks rules MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed anti_patterns regex that used brackets inside single quotes, which YAML interpreted as flow sequence syntax. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- .architecture-rules/background_tasks.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.architecture-rules/background_tasks.yaml b/.architecture-rules/background_tasks.yaml index 25ea3d59..217179a6 100644 --- a/.architecture-rules/background_tasks.yaml +++ b/.architecture-rules/background_tasks.yaml @@ -100,9 +100,9 @@ background_task_rules: - "error" -> "failed" severity: warning anti_patterns: - - pattern: 'status.*=.*["\']processing["\']' + - pattern: "status.*=.*processing" message: "Use 'running' instead of 'processing'" - - pattern: 'status.*=.*["\']fetching["\']' + - pattern: "status.*=.*fetching" message: "Use 'running' instead of 'fetching'" suggestion: | Use the standard status enum: