Skip to content

Conversation

@aralyekta
Copy link
Collaborator

@aralyekta aralyekta commented Jul 29, 2025

Summary by CodeRabbit

  • Documentation
    • Updated API documentation to include the new optional parameter fetch_existing for the answer endpoint.
    • Clarified the response formats for streaming and non-streaming requests.
    • Added a new example demonstrating how to use streaming and fetch the full answer with metadata using JavaScript.

@coderabbitai
Copy link

coderabbitai bot commented Jul 29, 2025

Walkthrough

The documentation for the POST /{guru_slug}/answer/ API endpoint was updated to add a new optional boolean parameter, fetch_existing. Clarifications were made regarding the response format when streaming is enabled, and new examples—including a detailed JavaScript code sample—were added to illustrate both streaming and full answer retrieval workflows.

Changes

Cohort / File(s) Change Summary
API Endpoint Documentation Update
api-reference/endpoints/ask-question.mdx
Added fetch_existing parameter documentation, clarified streaming vs. non-streaming response formats, and introduced new usage examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


🪧 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 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
api-reference/endpoints/ask-question.mdx (3)

34-36: Clarify fetch_existing behaviour and interaction with stream

The parameter description is helpful, but it leaves two open questions:

  1. Is fetch_existing=true incompatible with stream=true?
  2. Must the question body field exactly match a previous request, or is the slug also required?

Adding a single sentence covering these points removes guess-work for integrators.
Example:

Fetch an existing answer. When set to `true`, `stream` must be `false` and the
`question` must exactly match a prior request; otherwise a 404 is returned.

105-110: Code-fence language tag deviates from existing pattern

Other examples use the form ```json 200.
To stay consistent (and keep syntax-highlighters happy), drop the parentheses:

-```text 200 (stream=true)
+```text 200

The preceding prose already explains that this block corresponds to stream=true.


130-204: Wrap example in <CodeGroup> and avoid top-level await

  1. Docs guidelines encourage Mintlify components—wrapping the JS example in <CodeGroup> lets you add more languages later without re-structuring.
  2. Most readers will copy-paste; top-level await fails in non-ESM Node environments. Encapsulate calls in an async IIFE for broader compatibility.
-## Code Examples
-
-### Streaming and Fetching The Answer
-
-This example demonstrates how to stream a response and then fetch the complete answer with metadata.
-
-```javascript
+## Code Examples
+<CodeGroup>
+
+### JavaScript · Stream then fetch full answer
+
+```javascript
 (async () => {
   // Configuration
   const API_KEY = 'your-api-key-here';
@@
   const question = "Does Gurubase support Slack?";
 
-// 1. Ask with stream
-await askGurubase(question);
-
-// 2. Then fetch the answer from the db (for the JSON fields)
-await fetchExisting(question);
+  // 1️⃣ Stream the answer text
+  await askGurubase(question);
+
+  // 2️⃣ Retrieve full JSON (references, trust_score, etc.)
+  await fetchExisting(question);
+})();

+


This keeps the snippet self-contained, aligns with the component guidelines, and avoids run-time surprises.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 169ecd1a86c90cf8f84657e3a19c946501ceff68 and 54becc1a908cd288f6be4e245c52d0cb0783977a.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `api-reference/endpoints/ask-question.mdx` (4 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>📓 Path-based instructions (2)</summary>

<details>
<summary>**/*.mdx</summary>


**📄 CodeRabbit Inference Engine (CLAUDE.md)**

> `**/*.mdx`: Use MDX format for all documentation files
> Use Mintlify components like <Card>, <CardGroup>, <CodeGroup> for rich content
> Include practical examples and code snippets in documentation
> Use images from /images/ directory for visual guides

Files:
- `api-reference/endpoints/ask-question.mdx`

</details>
<details>
<summary>api-reference/endpoints/**/*.mdx</summary>


**📄 CodeRabbit Inference Engine (CLAUDE.md)**

> API endpoint docs follow the structure in /api-reference/endpoints/

Files:
- `api-reference/endpoints/ask-question.mdx`

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>api-reference/endpoints/ask-question.mdx (1)</summary>

`81-83`: **Good call-out on streaming vs JSON response**

This note eliminates a common confusion between the two response modes. 👍

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@fatihbaltaci fatihbaltaci merged commit ba7bbea into master Jul 29, 2025
3 checks passed
@fatihbaltaci fatihbaltaci deleted the task/api-ask-improvement branch July 29, 2025 14:42
@coderabbitai coderabbitai bot mentioned this pull request Jul 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants