Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lee/update citation format #504

Closed
wants to merge 2 commits into from
Closed

Conversation

leehuwuj
Copy link
Collaborator

@leehuwuj leehuwuj commented Feb 17, 2025

Merge after: run-llama/chat-ui#45

Summary by CodeRabbit

  • New Features
    • Enhanced the chat interface to boost user interaction.
    • Refined citation prompts, providing clearer guidance on formatting citations.
  • Chores
    • Upgraded the chat UI dependency to improve performance and reliability.

Copy link

changeset-bot bot commented Feb 17, 2025

🦋 Changeset detected

Latest commit: 40ae3a5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
create-llama Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

coderabbitai bot commented Feb 17, 2025

Walkthrough

The changes introduce a new patch named "create-llama" that updates the chat UI component and refines the citation prompt functionality. The citation prompt string is modified in the environment variables file to clarify how citations should be formatted and separated by spaces. Additionally, the dependency for the chat UI in the Next.js streaming template is updated from version 0.0.14 to 0.0.16.

Changes

File(s) Summary
.changeset/nasty-dingos-approve.md
templates/.../nextjs/package.json
Added the "create-llama" patch updating the chat-ui component and updated the dependency @llamaindex/chat-ui from 0.0.14 to 0.0.16.
helpers/env-variables.ts Modified the citationPrompt string in the getSystemPromptEnv function to refine citation formatting and separate multiple nodes.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as Chat UI Component
    participant E as Environment (Citation Formatter)

    U->>C: Send message/request
    C->>E: Retrieve updated citation prompt
    E-->>C: Return refined prompt with node_id instructions
    C-->>U: Display message with enhanced chat UI and citation formatting
Loading

Poem

I'm a little rabbit, hopping in the code,
"Create-llama" patch lighting up my humble abode.
The chat UI now gleams with a fresh design,
Citations dance in order, neat and fine.
Dependencies updated, a tech carrot delight,
Hopping along the changes, everything's just right!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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: 1

🧹 Nitpick comments (1)
helpers/env-variables.ts (1)

486-504: Enhance the citation prompt string handling and example.

While the citation format instructions are clear, there are two improvements that could be made:

  1. Use template literals instead of single quotes to avoid potential issues with apostrophes.
  2. Enhance the example to show more citation use cases.

Apply this diff to improve the prompt:

-    const citationPrompt = `'You have provided information from a knowledge base that separates the information into multiple nodes.
+    const citationPrompt = `You have provided information from a knowledge base that separates the information into multiple nodes.
 Always add a citation to each sentence or paragraph that you reference in the provided information using the node_id field in the header of each node.
 
 The citation format is: [citation:<node_id>]
 Where the <node_id> is the node_id field in the header of each node.
 Always separate the citation by a space.

 Example:
 We have two nodes:
   node_id: xyz
   file_name: llama.pdf
   
   node_id: abc
   file_name: animal.pdf

 Your answer with citations:
 A baby llama is called "Cria" [citation:xyz]
-It often lives in desert [citation:abc] [citation:xyz]
-'`;
+It often lives in desert [citation:abc] [citation:xyz]
+
+Multiple facts can be combined:
+Llamas are social animals that live in herds [citation:abc] and can carry up to 25-30% of their body weight [citation:xyz]`;
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9e723c3 and 40ae3a5.

📒 Files selected for processing (3)
  • .changeset/nasty-dingos-approve.md (1 hunks)
  • helpers/env-variables.ts (2 hunks)
  • templates/types/streaming/nextjs/package.json (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • .changeset/nasty-dingos-approve.md
  • templates/types/streaming/nextjs/package.json

@@ -483,11 +483,12 @@ const getSystemPromptEnv = (
});
}
if (tools?.length == 0 && (dataSources?.length ?? 0 > 0)) {
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix the condition for adding citation prompt.

The current condition has operator precedence and logical issues. The expression dataSources?.length ?? 0 > 0 is not correctly checking if there are data sources.

Apply this diff to fix the condition:

-  if (tools?.length == 0 && (dataSources?.length ?? 0 > 0)) {
+  if (tools?.length == 0 && ((dataSources?.length ?? 0) > 0)) {
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if (tools?.length == 0 && (dataSources?.length ?? 0 > 0)) {
if (tools?.length == 0 && ((dataSources?.length ?? 0) > 0)) {
🧰 Tools
🪛 Biome (1.9.4)

[error] 485-485: Comparing to itself is potentially pointless.

(lint/suspicious/noSelfCompare)

@leehuwuj
Copy link
Collaborator Author

Closed as it has already been implemented in #502

@leehuwuj leehuwuj closed this Feb 25, 2025
@leehuwuj leehuwuj deleted the lee/update-citation-format branch April 9, 2025 12:04
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.

1 participant