Fix content submission error handling and JSON parsing issues

[ishaileshpant]

🔧 Fix Content Submission Error Handling

Problem

Content submission was failing with "A server e... is not valid JSON" errors, indicating that the bot API was returning non-JSON responses (likely HTML error pages) when errors occurred.

Root Causes

1. Bot API error handling - Server errors were returning HTML instead of JSON
2. Frontend JSON parsing - No fallback handling for non-JSON error responses
3. Missing catch-all error handler - Some errors could bypass JSON response handling

Solution

• ✅ Enhanced error handling in frontend to handle non-JSON responses
• ✅ Added fallback parsing for error responses with raw text logging
• ✅ Added final catch-all error handler in bot API to ensure valid JSON responses
• ✅ Improved error messages for better debugging

Technical Changes

// Before - could fail on non-JSON responses
const errorData = await response.json();

// After - handles both JSON and non-JSON responses
let errorData;
try {
    errorData = await response.json();
} catch (jsonError) {
    const textResponse = await response.text();
    throw new Error(`Server error: ${response.status} - ${textResponse.substring(0, 100)}`);
}

Files Changed

• github-auth.js - Enhanced error handling in createPullRequest method
• api/github/create-content-pr.js - Added final catch-all error handler

Impact

• 🎯 Resolves "A server e... is not valid JSON" errors
• 🚀 Improves error handling and user experience
• 🔍 Enhances debugging with better error messages
• 🛡️ Prevents HTML error pages from breaking JSON parsing

Testing

• Error handling now works with both JSON and non-JSON responses
• Bot API always returns valid JSON responses
• Better error messages for debugging
• No linting errors

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
prepguides-dev	Ready	Preview	Comment	Oct 8, 2025 6:41pm

[ishaileshpant]

/approve

[github-actions]

🚀 Admin-Approved and Auto-Merged!

This PR has been automatically merged to main after admin approval by @ishaileshpant.

✅ **Status**: Merged and deployed
🔗 **Commit**: `faab75c5d8a12cd31884b6de54589234265e09cf`
📅 **Merged at**: 2025-10-08T18:42:07.294Z
👤 **Approved by**: Admin/Maintainer/Owner

Thank you for your contribution! 🎉