Skip to content

"Fix: Avoid double-wrapping JSON in DoStream" #287

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kowshickraj21
Copy link

@kowshickraj21 kowshickraj21 commented Apr 10, 2025

Proposed changes

Stream is now checked if it already a JSON and avoiding Double-Wrapping the JSON.

Types of changes

  • [ X ] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update or tests (if none of the other choices apply)

Checklist

  • [ X ] I have read the CONTRIBUTING doc
  • I have lint'ed all of my code using repo standards
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

Considered creating another Function DoJSON but it is not needed as the change is very subtle.

Summary by CodeRabbit

  • New Features
    • Improved text input processing now automatically detects valid JSON, enabling a more streamlined handling of inputs.

Copy link

coderabbitai bot commented Apr 10, 2025

Walkthrough

The changes update the DoText method in the Client struct. The method now checks if the provided text is valid JSON by attempting to unmarshal it. It verifies the existence of a "text" field and, if valid, writes the original JSON text to the buffer after logging. Otherwise, it encodes the input as a textSource struct before writing. Error handling for write operations remains unchanged, and there are no public API alterations.

Changes

File Change Summary
pkg/client/.../client.go Modified DoText to unmarshal input text into a temporary map, check for the "text" field, and conditionally log and write either the original text or an encoded textSource to a buffer.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Parser
    participant Buffer

    Client->>Parser: Attempt to unmarshal input text
    alt Valid JSON with "text" field exists
        Parser-->>Client: isValidJSON = true
        Client->>Client: Log "Input is already JSON"
        Client->>Buffer: Write original text
        alt Write operation fails
            Buffer-->>Client: Return error
        else Write operation succeeds
            Buffer-->>Client: Return success
        end
    else
        Parser-->>Client: isValidJSON = false
        Client->>Client: Encode text as textSource struct
        Client->>Buffer: Write encoded text
        Buffer-->>Client: Return result or error
    end
Loading

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b53efc5 and d91ecf6.

📒 Files selected for processing (1)
  • pkg/client/analyze/v1/client.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pkg/client/analyze/v1/client.go

🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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: 1

🧹 Nitpick comments (6)
pkg/client/analyze/v1/client.go (6)

149-154: Consider additional logging for JSON parsing failures

When JSON unmarshaling fails, this is valuable debugging information that is currently not logged.

 	if err := json.Unmarshal([]byte(text), &tmp); err == nil {
 		// It's valid JSON, now check if it already contains a "text" field
 		if val, exists := tmp["Text"]; exists && val != nil {
 			isValidJSON = true
 		}
+	} else {
+		klog.V(6).Infof("Input is not valid JSON. Err: %v\n", err)
 	}

157-163: Fix incorrect package name in log message

The error log message references speak.DoText() but this is in the analyze package.

 	if isValidJSON {
 		klog.V(6).Infof("Is Already JSON \n")
 		_,err = buf.WriteString(text)
 		if err != nil {
 			klog.V(1).Infof("JSON WriteString failed. Err: %v\n", err)
-			klog.V(6).Infof("speak.DoText() LEAVE\n")
+			klog.V(6).Infof("analyze.DoText() LEAVE\n")
 			return err
 		}

157-157: Enhance log message for better debugging

The current log message could be more descriptive to aid in debugging.

-		klog.V(6).Infof("Is Already JSON \n")
+		klog.V(6).Infof("Input already contains valid JSON with 'text' field, skipping re-encoding\n")

151-153: Validate the type of the Text field

The code checks if the "Text" field exists and is not nil, but doesn't verify that it's a string, which could lead to issues later.

-		if val, exists := tmp["Text"]; exists && val != nil {
+		if val, exists := tmp["text"]; exists && val != nil {
+			// Verify that the value is a string
+			if _, ok := val.(string); ok {
 			isValidJSON = true
+			}
 		}

158-158: Fix missing space after comma

There's a formatting issue with a missing space after the comma in the function call.

-		_,err = buf.WriteString(text)
+		_, err = buf.WriteString(text)

163-164: Remove unnecessary trailing whitespace

There's unnecessary trailing whitespace at the end of line 163.

 			return err
 		}
-		
+
 	} else {
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bd4d246 and b53efc5.

📒 Files selected for processing (1)
  • pkg/client/analyze/v1/client.go (1 hunks)
🔇 Additional comments (1)
pkg/client/analyze/v1/client.go (1)

146-172: Feature implementation looks good, with suggested fixes

The overall approach to prevent double-wrapping JSON by checking if the input is already in JSON format is sound and addresses the PR objectives. With the suggested fixes above, this will effectively solve the issue of double-wrapping JSON in DoStream.

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