improvement(supabase): added more verbose error logging for supabase operations

[waleedlatif1]

Summary

added more verbose error logging for supabase operations

Type of Change

• Bug fix

Testing

tested manually, screenshots below

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Aug 19, 2025 8:37pm
sim	Building	Preview	Comment	Aug 19, 2025 8:37pm

[greptile-apps]

Greptile Summary

This PR enhances error handling and logging across all Supabase tools in the platform by implementing more verbose error messages and consistent response formatting. The changes affect seven files: six Supabase tool implementations (insert.ts, update.ts, delete.ts, query.ts, get_row.ts) and one block configuration file (blocks/supabase.ts), plus documentation updates.

Key improvements include:

Enhanced JSON Parsing: All tools now wrap JSON.parse() calls in try-catch blocks, throwing descriptive errors like Failed to parse Supabase response: ${parseError} instead of silently failing or providing generic messages.

Improved Success Messages: Tools now provide specific feedback with row counts (e.g., "Successfully updated 3 rows" vs generic "Successfully updated data") and proper pluralization handling.

Better Zero-Result Handling: Operations that affect zero rows now clearly distinguish between "no matching records found" versus actual errors, providing users with more actionable feedback.

API Consistency: The get_row tool was updated to return arrays instead of single objects/null, aligning with other Supabase tools' response patterns and making the API more predictable.

Enhanced Block Configuration: The Supabase block now provides detailed JSON parsing error messages with syntax guidance, helping users understand exactly what's wrong with their JSON data.

These changes create a cohesive error handling pattern across all Supabase operations, addressing a common pain point where users received generic or unclear error messages when database operations failed. The improvements are particularly valuable in a no-code/low-code platform where users need clear, actionable feedback to successfully configure their workflows.

Confidence score: 4/5

• This PR is safe to merge with good improvements to error handling and user experience
• Score reflects well-structured error handling improvements with minimal risk of breaking existing functionality
• Pay close attention to get_row.ts due to the breaking API change from single object to array response

_{7 files reviewed, 2 comments}

_{Edit Code Review Bot Settings | Greptile}