refactor: Change blocked to flagged

[dkorecko]

Summary by CodeRabbit

• Refactor

  • Renamed card status from “Blocked” to “Flagged” across the app (card view, menus, dialogs).
  • Existing blocked cards now appear as flagged; toggle action text and icons updated.
  • Cloned and recurring cards preserve the flagged state.
  • Any filters or displays referencing this status now use “Flagged.”

• Chores

  • Database updated to align with the new status name; no user action required.

[coderabbitai]

Walkthrough

Renames the Card entity boolean property from Blocked to Flagged. Adds an EF Core migration (designer, migration class, and updated model snapshot) to rename the Cards table column accordingly. Updates server-side logic in RepeatHostedService to set Flagged on new repeated cards. Updates UI components CloneBoardModal.razor and CardView.razor to read, toggle, and display Flagged instead of Blocked, including renaming a local method and adjusting labels. No additional structural or behavioral changes beyond the property/column rename and corresponding references.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 60.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “refactor: Change blocked to flagged” directly reflects the primary change of renaming the Blocked property to Flagged across the codebase, is concise, and uses clear phrasing indicating a refactor, making it easy for reviewers to understand the main intent at a glance.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch refactor/blocked-to-flagged

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 80e8b09 and 08ba2bb.

📒 Files selected for processing (7)

• Ticky.Base/Entities/Card.cs (1 hunks)
• Ticky.Internal/Migrations/20251005111419_BlockToFlagged.Designer.cs (1 hunks)
• Ticky.Internal/Migrations/20251005111419_BlockToFlagged.cs (1 hunks)
• Ticky.Internal/Migrations/DataContextModelSnapshot.cs (1 hunks)
• Ticky.Internal/Services/Hosted/RepeatHostedService.cs (1 hunks)
• Ticky.Web/Components/Dialogs/CloneBoardModal.razor (1 hunks)
• Ticky.Web/Components/Elements/CardView.razor (5 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (csharp)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}