Conversation
- Implement new `relevance` filter in evidence tasks list - Add `isNotRelevant` field to OrganizationEvidence model - Create server action `toggleRelevance` to mark evidence as relevant/not relevant - Update evidence details, filters, and data table to support relevance status - Enhance EvidenceTableProvider with relevance state management - Add relevance column and filter dropdown in evidence tasks view - Improve UI with visual indicators for evidence relevance
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
Caution Review failedThe pull request is closed. WalkthroughThis pull request implements several changes focused on evidence task relevance. The logic for counting and filtering evidence tasks has been refined, introducing a new "relevance" parameter throughout the codebase. UI components such as filter badges, dropdowns, and data table columns have been updated to display relevance status. A new action for toggling relevance has been added with corresponding UI updates in evidence details and review sections. Additionally, state management hooks and context have been extended to support the new relevance filtering, and the database schema has been modified to include a new boolean column with restructured enums for clarity. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant ED as EvidenceDetails Component
participant API as toggleRelevance Action
participant DB as Database
U->>ED: Click toggle relevance button
ED->>API: Call toggleRelevance (evidence ID, new flag)
API->>DB: Retrieve evidence record by ID & organization
DB-->>API: Return evidence record
API->>DB: Update evidence (relevance, published status, timestamp)
DB-->>API: Return updated evidence
API-->>ED: Respond with success and updated data
ED->>U: UI reflects new relevance status
sequenceDiagram
participant U as User
participant FD as FilterDropdown Component
participant CT as EvidenceTable Context
participant API as getOrganizationEvidenceTasks
participant DB as Database
U->>FD: Select relevance filter option
FD->>CT: Update relevance state
CT->>API: Fetch evidence tasks with relevance filter
API->>DB: Query tasks using relevance condition
DB-->>API: Return filtered tasks
API-->>CT: Provide updated task list
CT->>FD: UI updates with filtered results
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (17)
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Summary by CodeRabbit
New Features
UI Enhancements