ECHO-276 Split query ts file v1 by ussaama · Pull Request #236 · Dembrane/echo

ussaama · 2025-07-22T15:38:36Z

Summary by CodeRabbit

New Features
- Introduced modular React hooks for authentication, chat, conversation, participant, project, report, resource, unsubscribe, dropzone, library, and view management, enhancing scalability and maintainability.
- Added comprehensive user feedback via toast notifications and detailed upload progress and error tracking.
Refactor
- Reorganized hooks by relocating them from a centralized module to feature-specific directories for improved code clarity and separation of concerns.
- Removed a large shared query module, distributing its functionality into focused, domain-specific modules.
Bug Fixes
- Enhanced error handling with consistent messaging and rollback support during mutations and uploads.
Chores
- Updated import paths across the codebase to align with the new modular hook structure, ensuring consistent and reliable hook usage.

- Updated multiple components to import hooks from local paths instead of the centralized query file, improving modularity and maintainability. - Adjusted imports in ChatAccordion, AutoSelectConversations, ConversationAccordion, and other components to streamline code organization. - Enhanced clarity and consistency in the codebase by ensuring that related hooks are grouped together within their respective component directories.

- Deleted several unused hooks including useResourcesByProjectId and useDeleteConversationChunkByIdMutation to streamline the codebase. - Commented out the useConversationTokenCount function for potential future use, enhancing code clarity. - Cleaned up the query.ts file to improve maintainability and reduce clutter.

- Removed several unused hooks from query.ts to streamline the codebase. - Updated component imports to utilize local hooks instead of centralized query functions, enhancing code organization and maintainability. - Adjusted imports in ProjectLibrary, ProjectLibraryAspect, ProjectLibraryInsight, and ProjectLibraryView components for better modularity.

- Eliminated unused imports including getProjectInsights, getProjectViews, and getResourcesByProjectId to enhance code clarity and maintainability. - Focused on reducing clutter in the query.ts file, aligning with recent efforts to improve modularity and organization in the codebase.

…m the conversation hooks module.

- Updated imports in various components to source hooks from their respective directories under "@/components". - Introduced a new hook for fetching project conversation counts in the hooks index file. - Removed unused hooks from the query module to streamline functionality.

linear · 2025-07-22T15:38:39Z

ECHO-276 split up query.ts

coderabbitai · 2025-07-22T15:38:45Z

Caution

Review failed

The pull request is closed.

Walkthrough

This change splits the large query.ts file into multiple domain-specific hook modules across the frontend codebase. All React Query hooks for authentication, chat, conversation, dropzone, library, participant, project, report, resource, unsubscribe, and view functionalities are now defined in their respective hooks/index.ts files. All components and routes update their imports to use these new modules, while the monolithic query.ts is removed entirely.

Changes

File(s)	Change Summary
`echo/frontend/src/lib/query.ts`	Removed entire file containing all React Query hooks and utilities; hooks redistributed to domain-specific modules.
`echo/frontend/src/components/auth/hooks/index.ts` `.../chat/hooks/index.ts` `.../conversation/hooks/index.ts` `.../dropzone/hooks/index.ts` `.../library/hooks/index.ts` `.../participant/hooks/index.ts` `.../project/hooks/index.ts` `.../report/hooks/index.ts` `.../resource/hooks/index.ts` `.../unsubscribe/hooks/index.ts` `.../view/hooks/index.ts`	Added new domain-specific React Query hook modules encapsulating queries and mutations for each feature area.
Multiple components and routes (e.g., `ChatAccordion.tsx`, `ConversationAccordion.tsx`, `ProjectSidebar.tsx`, `ReportRenderer.tsx`, `ParticipantConversation.tsx`, `ProjectLibrary.tsx`, `ProjectReportRoute.tsx`, `ProjectResourceOverview.tsx`, `ProjectUnsubscribe.tsx`, etc.)	Updated imports to reference the new domain-specific hook modules instead of the removed `@/lib/query`.
`echo/frontend/src/components/auth/utils/errorUtils.ts`	Added `throwWithMessage` utility function for consistent error handling in auth hooks.

Sequence Diagram(s)

sequenceDiagram
    participant Component
    participant DomainHooks
    participant API/Directus
    Note over Component,DomainHooks: Example: Using a domain-specific hook
    Component->>DomainHooks: Call useSomeDomainMutation()
    DomainHooks->>API/Directus: Perform async API/mutation
    API/Directus-->>DomainHooks: Return result/error
    DomainHooks-->>Component: Update state, trigger toasts, navigate, etc.

Estimated code review effort

5 (~2+ hours). This is a large-scale, high-complexity refactor with many new files, significant code movement, and touchpoints across the entire frontend codebase. Each new hook module contains substantial logic that must be reviewed for correctness, consistency, and parity with the prior implementation.

Possibly related PRs

ECHO-276 Split query ts file v1 #236: Introduces the same echo/frontend/src/components/auth/hooks/index.ts module with React Query hooks for authentication, indicating direct relation.

Suggested reviewers

spashii

LGTM.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 500ae75 and f77918b.

📒 Files selected for processing (1)

echo/docs/modular_component_pattern.md (1 hunks)

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 9

🔭 Outside diff range comments (3)

echo/frontend/src/routes/auth/VerifyEmail.tsx (1)
15-21: 🛑 Early-return on missing token to avoid useless API round-trip

handleVerify() alerts when token is null but still calls verifyMutation.mutate with an empty string. That hits the backend with guaranteed failure and spams the error toast.
   const token = search.get("token");
   if (!token) {
     window.alert(t`Invalid token. Please try again.`);
+    return; // bail fast
   }

   verifyMutation.mutate({ token: token ?? "" });
echo/frontend/src/components/report/ConversationStatusTable.tsx (1)
30-36: 💡 Only surface this widget when there’s work to do

Per prior UX guidance (ECHO-224), the status section should disappear when pendingConversations.length === 0. Current guard shows table whenever any conversation exists, including all-finished cases. Consider tweaking:
-const conversations = [...];
-if (conversations.length === 0) return null;
+const conversations = [...];
+const hasPending = conversations.some(c => !c.is_finished);
+if (!hasPending) return null;
echo/frontend/src/routes/participant/ParticipantPostConversation.tsx (1)
41-92: Dead isCheckingEmail state & missing timeout cleanup

isCheckingEmail is never toggled and the debounce setTimeout isn’t cleared on unmount, leaving hanging timers in long-lived sessions.
-const [isCheckingEmail, setIsCheckingEmail] = useState(false);
+// remove unless a future MX lookup is planned
If debouncing stays:
useEffect(() => () => debounceTimeout && clearTimeout(debounceTimeout), [debounceTimeout]);

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4139137 and 63387b2.

📒 Files selected for processing (47)

echo/frontend/src/components/auth/hooks/index.ts (1 hunks)
echo/frontend/src/components/chat/ChatAccordion.tsx (1 hunks)
echo/frontend/src/components/chat/hooks/index.ts (1 hunks)
echo/frontend/src/components/conversation/AutoSelectConversations.tsx (1 hunks)
echo/frontend/src/components/conversation/ConversationAccordion.tsx (1 hunks)
echo/frontend/src/components/conversation/ConversationChunkAudioTranscript.tsx (1 hunks)
echo/frontend/src/components/conversation/ConversationDangerZone.tsx (1 hunks)
echo/frontend/src/components/conversation/ConversationEdit.tsx (1 hunks)
echo/frontend/src/components/conversation/MoveConversationButton.tsx (1 hunks)
echo/frontend/src/components/conversation/hooks/index.ts (1 hunks)
echo/frontend/src/components/dropzone/UploadConversationDropzone.tsx (1 hunks)
echo/frontend/src/components/dropzone/hooks/index.ts (1 hunks)
echo/frontend/src/components/library/hooks/index.ts (1 hunks)
echo/frontend/src/components/participant/ParticipantInitiateForm.tsx (1 hunks)
echo/frontend/src/components/participant/hooks/index.ts (1 hunks)
echo/frontend/src/components/project/ProjectDangerZone.tsx (1 hunks)
echo/frontend/src/components/project/ProjectSidebar.tsx (1 hunks)
echo/frontend/src/components/project/ProjectTagsInput.tsx (2 hunks)
echo/frontend/src/components/project/hooks/index.ts (1 hunks)
echo/frontend/src/components/report/ConversationStatusTable.tsx (1 hunks)
echo/frontend/src/components/report/CreateReportForm.tsx (1 hunks)
echo/frontend/src/components/report/ReportRenderer.tsx (1 hunks)
echo/frontend/src/components/report/ReportTimeline.tsx (1 hunks)
echo/frontend/src/components/report/UpdateReportModalButton.tsx (1 hunks)
echo/frontend/src/components/report/hooks/index.ts (1 hunks)
echo/frontend/src/components/resource/hooks/index.ts (1 hunks)
echo/frontend/src/components/unsubscribe/hooks/index.ts (1 hunks)
echo/frontend/src/components/view/CreateViewForm.tsx (1 hunks)
echo/frontend/src/components/view/hooks/index.ts (1 hunks)
echo/frontend/src/lib/query.ts (1 hunks)
echo/frontend/src/routes/auth/Login.tsx (1 hunks)
echo/frontend/src/routes/auth/PasswordReset.tsx (1 hunks)
echo/frontend/src/routes/auth/Register.tsx (1 hunks)
echo/frontend/src/routes/auth/RequestPasswordReset.tsx (1 hunks)
echo/frontend/src/routes/auth/VerifyEmail.tsx (1 hunks)
echo/frontend/src/routes/participant/ParticipantConversation.tsx (1 hunks)
echo/frontend/src/routes/participant/ParticipantPostConversation.tsx (1 hunks)
echo/frontend/src/routes/participant/ParticipantReport.tsx (1 hunks)
echo/frontend/src/routes/project/chat/ProjectChatRoute.tsx (1 hunks)
echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx (1 hunks)
echo/frontend/src/routes/project/conversation/ProjectConversationTranscript.tsx (1 hunks)
echo/frontend/src/routes/project/library/ProjectLibrary.tsx (1 hunks)
echo/frontend/src/routes/project/library/ProjectLibraryAspect.tsx (1 hunks)
echo/frontend/src/routes/project/library/ProjectLibraryView.tsx (1 hunks)
echo/frontend/src/routes/project/report/ProjectReportRoute.tsx (1 hunks)
echo/frontend/src/routes/project/resource/ProjectResourceOverview.tsx (1 hunks)
echo/frontend/src/routes/project/unsubscribe/ProjectUnsubscribe.tsx (1 hunks)

🧠 Learnings (26)

📓 Common learnings

Learnt from: ussaama
PR: Dembrane/echo#205
File: echo/frontend/src/lib/query.ts:1444-1506
Timestamp: 2025-07-10T12:48:20.683Z
Learning: ussaama prefers string concatenation over template literals for simple cases where readability is clearer, even when linting tools suggest template literals. Human readability takes precedence over strict linting rules in straightforward concatenation scenarios.

echo/frontend/src/components/report/ConversationStatusTable.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/routes/participant/ParticipantPostConversation.tsx (2)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

echo/frontend/src/routes/project/unsubscribe/ProjectUnsubscribe.tsx (1)

Learnt from: ussaama
PR: #185
File: echo/frontend/src/App.tsx:25-36
Timestamp: 2025-06-16T11:51:33.799Z
Learning: In echo/frontend/src/App.tsx, user ussaama prefers explicit code over terse/inline code for React useEffect cleanup functions, choosing clarity and future maintainability over brevity when assigning cleanup functions to variables before returning them.

echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx (2)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

echo/frontend/src/components/conversation/ConversationDangerZone.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/report/UpdateReportModalButton.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/conversation/ConversationEdit.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/report/CreateReportForm.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/conversation/AutoSelectConversations.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/routes/project/conversation/ProjectConversationTranscript.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/project/ProjectTagsInput.tsx (2)

Learnt from: ussaama
PR: #169
File: echo/frontend/src/components/project/ProjectPortalEditor.tsx:409-464
Timestamp: 2025-05-30T15:38:44.413Z
Learning: Badge-based selectors in ProjectPortalEditor.tsx: Keyboard navigation enhancements for accessibility are considered optional improvements rather than critical issues. The user acknowledges these suggestions but doesn't prioritize them as blockers.

Learnt from: ussaama
PR: #185
File: echo/frontend/src/App.tsx:10-15
Timestamp: 2025-06-16T11:48:51.114Z
Learning: In echo/frontend project, ussaama prefers to defer import refactoring (like grouping config imports under a namespace) until the import list grows significantly, following a pragmatic approach to technical debt management.

echo/frontend/src/routes/project/library/ProjectLibraryAspect.tsx (1)

Learnt from: ussaama
PR: #185
File: echo/frontend/src/App.tsx:25-36
Timestamp: 2025-06-16T11:51:33.799Z
Learning: In echo/frontend/src/App.tsx, user ussaama prefers explicit code over terse/inline code for React useEffect cleanup functions, choosing clarity and future maintainability over brevity when assigning cleanup functions to variables before returning them.

echo/frontend/src/routes/participant/ParticipantConversation.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/components/conversation/ConversationAccordion.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

echo/frontend/src/routes/project/report/ProjectReportRoute.tsx (1)

Learnt from: ussaama
PR: #169
File: echo/frontend/src/components/project/ProjectPortalEditor.tsx:409-464
Timestamp: 2025-05-30T15:38:44.413Z
Learning: Badge-based selectors in ProjectPortalEditor.tsx: Keyboard navigation enhancements for accessibility are considered optional improvements rather than critical issues. The user acknowledges these suggestions but doesn't prioritize them as blockers.

echo/frontend/src/components/unsubscribe/hooks/index.ts (1)

Learnt from: ussaama
PR: #185
File: echo/frontend/src/App.tsx:25-36
Timestamp: 2025-06-16T11:51:33.799Z
Learning: In echo/frontend/src/App.tsx, user ussaama prefers explicit code over terse/inline code for React useEffect cleanup functions, choosing clarity and future maintainability over brevity when assigning cleanup functions to variables before returning them.

echo/frontend/src/components/conversation/hooks/index.ts (3)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

echo/frontend/src/components/auth/hooks/index.ts (2)

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/hooks/useProcessedAnnouncements.ts:17-18
Timestamp: 2025-07-03T13:30:40.981Z
Learning: In the echo frontend codebase, Directus types like Announcement are globally available and do not require explicit imports. The types are resolved through the Directus type system configuration in files like echo/frontend/src/lib/typesDirectus.d.ts and echo/frontend/src/lib/typesDirectusContent.ts.

echo/frontend/src/components/dropzone/hooks/index.ts (2)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

echo/frontend/src/components/report/hooks/index.ts (2)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

echo/frontend/src/components/project/hooks/index.ts (3)

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/hooks/useProcessedAnnouncements.ts:17-18
Timestamp: 2025-07-03T13:30:40.981Z
Learning: In the echo frontend codebase, Directus types like Announcement are globally available and do not require explicit imports. The types are resolved through the Directus type system configuration in files like echo/frontend/src/lib/typesDirectus.d.ts and echo/frontend/src/lib/typesDirectusContent.ts.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/hooks/index.ts:23-36
Timestamp: 2025-07-03T13:34:59.482Z
Learning: In the echo frontend codebase, using @ts-ignore for Directus SDK filter type issues is acceptable and preferred over extending types or using workarounds. This applies specifically to date comparisons and other filter operations where the SDK types may not be perfectly aligned.

echo/frontend/src/components/participant/hooks/index.ts (3)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.295Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

echo/frontend/src/components/chat/hooks/index.ts (2)

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

echo/frontend/src/components/library/hooks/index.ts (3)

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/hooks/useProcessedAnnouncements.ts:17-18
Timestamp: 2025-07-03T13:30:40.981Z
Learning: In the echo frontend codebase, Directus types like Announcement are globally available and do not require explicit imports. The types are resolved through the Directus type system configuration in files like echo/frontend/src/lib/typesDirectus.d.ts and echo/frontend/src/lib/typesDirectusContent.ts.

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/hooks/index.ts:23-36
Timestamp: 2025-07-03T13:34:59.482Z
Learning: In the echo frontend codebase, using @ts-ignore for Directus SDK filter type issues is acceptable and preferred over extending types or using workarounds. This applies specifically to date comparisons and other filter operations where the SDK types may not be perfectly aligned.

echo/frontend/src/lib/query.ts (2)

Learnt from: ussaama
PR: #202
File: echo/frontend/src/components/announcement/AnnouncementIcon.tsx:19-19
Timestamp: 2025-07-03T15:47:56.584Z
Learning: In the echo frontend codebase, type assertions like as Announcement are necessary when using data returned from Directus SDK hooks like useLatestAnnouncement() because the SDK returns generic types that TypeScript cannot automatically infer as the specific Directus collection types, even though the types are globally available.

Learnt from: spashii
PR: #142
File: echo/frontend/src/lib/query.ts:730-740
Timestamp: 2025-05-13T15:18:29.107Z
Learning: When working with Directus API in this codebase, foreign key relationships must be specified using nested objects with id properties (e.g., conversation_id: { id: conversationId } as Conversation) rather than direct ID values, even though this appears redundant.

🧬 Code Graph Analysis (6)

echo/frontend/src/components/view/hooks/index.ts (2)

echo/frontend/src/lib/api.ts (1)

generateProjectView (669-680)

echo/frontend/src/components/common/Toaster.tsx (1)

toast (34-34)

echo/frontend/src/components/unsubscribe/hooks/index.ts (1)

echo/frontend/src/lib/api.ts (1)

checkUnsubscribeStatus (859-872)

echo/frontend/src/components/resource/hooks/index.ts (2)

echo/frontend/src/lib/api.ts (3)

updateResourceById (140-148)

deleteResourceById (150-152)

getResourceById (136-138)

echo/frontend/src/components/common/Toaster.tsx (1)

toast (34-34)

echo/frontend/src/components/conversation/hooks/index.ts (3)

echo/server/dembrane/reply_utils.py (1)

Conversation (27-31)

echo/frontend/src/lib/api.ts (7)

deleteConversationById (847-856)

addChatContext (706-718)

deleteChatContext (720-732)

getConversationChunkContentLink (653-658)

apiNoAuth (17-17)

retranscribeConversation (690-700)

getConversationTranscriptString (682-688)

echo/frontend/src/components/common/Toaster.tsx (1)

toast (34-34)

echo/frontend/src/components/dropzone/hooks/index.ts (2)

echo/frontend/src/lib/api.ts (2)

initiateAndUploadConversationChunk (499-626)

uploadResourceByProjectId (154-174)

echo/frontend/src/components/common/Toaster.tsx (1)

toast (34-34)

echo/frontend/src/components/library/hooks/index.ts (2)

echo/frontend/src/lib/api.ts (2)

getProjectViews (195-215)

generateProjectLibrary (660-667)

echo/frontend/src/components/common/Toaster.tsx (1)

toast (34-34)

🪛 Biome (1.9.4)

echo/frontend/src/components/conversation/hooks/index.ts

[error] 263-263: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

[error] 308-308: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

[error] 542-542: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)

[error] 598-598: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)

echo/frontend/src/components/auth/hooks/index.ts

[error] 70-70: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)

echo/frontend/src/components/report/hooks/index.ts

[error] 241-241: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)

[error] 242-242: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)

echo/frontend/src/components/participant/hooks/index.ts

[error] 85-85: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

[error] 104-104: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

[error] 181-181: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

[error] 200-200: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

🧰 Additional context used

🧠 Learnings (26)

📓 Common learnings

Learnt from: ussaama
PR: Dembrane/echo#205
File: echo/frontend/src/lib/query.ts:1444-1506
Timestamp: 2025-07-10T12:48:20.683Z
Learning: ussaama prefers string concatenation over template literals for simple cases where readability is clearer, even when linting tools suggest template literals. Human readability takes precedence over strict linting rules in straightforward concatenation scenarios.