testing pr

[sajdakabir]

What did you ship?

Fixes:

• #XXX (GitHub issue number)
• MAR-XXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Checklist:

• I have self-reviewed the code (A decent size PR without self-review might be rejected)
• I pinky swear that my codes gonna work as I have testing every possible scenario.
• I ignored Coderabbit suggestion because it does not make any sense.
• I took Coderabbit suggestion under consideration as some of it makes sense.
• I have commented my code, particularly in hard-to-understand areas.

OR:

• shut up and let me cook.

---

Important

This PR enhances AI response handling, adds support for detecting unsupported features, and updates frontend components for improved user interaction.

• AI Enhancements:
  • Added caching and error handling to generateResponse in ai.route.js.
  • Implemented rate limiting and memory management for user interactions in ai.route.js.
  • Enhanced QueryUnderstanding in query.service.js to handle unsupported features and list all queries.
• Unsupported Features:
  • Added handling for unsupported features like calendar and email in query.service.js.
  • Provides user with alternative actions when unsupported features are requested.
• Frontend Updates:
  • Integrated MarkdownText for rendering AI responses in agent.tsx.
  • Updated useEvents hook to handle calendar connection status and optimize event fetching.

^{This description was created by for efa45b9. You can customize this summary. It will automatically update as commits are pushed.}

[github-actions]

Hey there! 👋

We require pull request titles to follow the Conventional Commits specification.

Valid types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

Format: type: description

Error details:

No release type found in pull request title "testing pr". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat
 - fix
 - docs
 - ui
 - refac
 - perf
 - test
 - build
 - ci
 - chore
 - revert

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to efa45b9 in 3 minutes and 9 seconds. Click for details.

• Reviewed 1877 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 9 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. apps/backend/src/routers/ai/ai.route.js:19

• Draft comment:
  Good initialization of GoogleGenerativeAI with warning if API key is missing.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. apps/backend/src/routers/ai/ai.route.js:54

• Draft comment:
  Cache key generation uses JSON.stringify; ensure consistent ordering of keys in context to avoid cache misses.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50% None

3. apps/backend/src/routers/ai/ai.route.js:148

• Draft comment:
  Improve error handling for AI response fallback.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. apps/web/src/components/agent/agent.tsx:145

• Draft comment:
  Wrap MessagePrimitive.Content with MarkdownText for rich text rendering – good usage of components prop.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. apps/web/src/hooks/use-events.ts:27

• Draft comment:
  Query function correctly returns an empty array if calendar not connected.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

6. apps/web/src/hooks/use-events.ts:56

• Draft comment:
  Optimistic updates properly snapshot previous events; ensure type-safety of events array.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

7. apps/backend/src/utils/query.service.js:822

• Draft comment:
  Consider refactoring the natural language date parsing logic (used in both update and creation intents) into a shared helper to reduce duplication and improve maintainability.
• Reason this comment was not posted:
  Comment was on unchanged code.

8. apps/web/src/components/agent/agent.tsx:145

• Draft comment:
  Good integration of MarkdownText in MessagePrimitive.Content. Verify that the MarkdownText component properly handles all required markdown formatting in various message scenarios.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify the behavior of the MarkdownText component, which violates the rule against asking for confirmation or verification of behavior. It does not provide a specific suggestion or point out a specific issue.

9. apps/web/src/hooks/use-events.ts:34

• Draft comment:
  In the useQuery hook, consider including 'isCalendarConnected' in the 'enabled' condition to avoid unnecessary query execution when the calendar isn’t connected.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The current implementation is actually better than the suggested change. By handling isCalendarConnected in the queryFn, it allows the cache to maintain an empty array state when disconnected, rather than having an undefined state that would need to be handled elsewhere. This is a more robust approach that maintains consistent data types. The comment's suggestion could potentially prevent unnecessary function calls to the queryFn, which might be marginally more efficient. The current implementation's benefits of consistent data typing and caching behavior outweigh the minimal performance impact, especially since the queryFn's check is very lightweight. The comment should be deleted as it suggests a change that would make the code less robust than the current implementation.

Workflow ID: wflow_8F6lNDCMHV8Djb5s

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Avoid redeclaring isListAllQuery; it’s already defined on line 65. Remove the duplicate declaration to prevent shadowing.

Suggested change

const isListAllQuery = context.parameters?.metadata?.listAll === true;

^{This comment was generated because it violated a code review rule: irule_gq6emKKMBQaj1soO.}