avoid serializing optimized code

[mohammedahmed18]

PR Type

Bug fix

---

Description

• Remove JSON serialization of optimized code

• Return raw optimized source in optimization

• Remove unused json import

---

Changes walkthrough 📝

	Relevant files
Bug fix	beta.py` Remove JSON serialization in optimization output                  codeflash/lsp/beta.py Deleted import json statement Replaced json.dumps call with raw optimized_source Updated optimization return field to raw string
Additional files	beta.py +1/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Downstream JSON serialization Returning the raw optimized_source string, which may contain newlines or special characters, could lead to invalid JSON or formatting issues if not escaped properly by downstream serializers. Ensure callers handle escaping correctly. "optimization": optimized_source, }

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Limit code payload size Truncate or paginate very large optimized_source outputs to prevent exceeding client or transport size limits. You can slice to a defined MAX_CODE_LENGTH and append an ellipsis or provide a link to the full code. codeflash/lsp/beta.py [230] -"optimization": optimized_source, +"optimization": ( + optimized_source[:MAX_CODE_LENGTH] + "..." + if len(optimized_source) > MAX_CODE_LENGTH + else optimized_source +), Suggestion importance[1-10]: 5 __ Why: Truncating large payloads can prevent transport issues and improve performance, but may clip necessary data and should be balanced against user needs.	Low
Possible issue	Escape code for JSON safety Escape special characters in optimized_source so that the final JSON payload remains valid if your framework does not automatically handle escaping. Using Unicode-escape ensures newlines and quotes don’t break the JSON structure. codeflash/lsp/beta.py [230] -"optimization": optimized_source, +"optimization": optimized_source.encode("unicode_escape").decode("ascii"), Suggestion importance[1-10]: 4 __ Why: Manually escaping via unicode-escape is redundant since standard JSON serializers handle special characters automatically, making this change of limited benefit.	Low