fix: preserve comment content when resolving comments#28
Merged
a-bonus merged 7 commits intoa-bonus:mainfrom Nov 29, 2025
Merged
fix: preserve comment content when resolving comments#28a-bonus merged 7 commits intoa-bonus:mainfrom
a-bonus merged 7 commits intoa-bonus:mainfrom
Conversation
- Fixes 'could not infer client capabilities' warnings - Improves MCP connection stability and reliability - Includes built-in completions capability (no patching needed) - Better timeout handling for API requests
- getDocumentInfo: Remove 'permissions' and 'alternateLink' fields that cause 'Invalid field selection' errors for Google Docs files - applyParagraphStyle: Fix alignment enum to use START/END instead of LEFT/RIGHT per Google Docs API internationalization requirements - applyParagraphStyle: Simplify target parameter by removing redundant applyToContainingParagraph field (was always true)
- Add 'Known Limitations' section to README documenting: - Comment anchoring limitations (Drive API v3) - Comment resolution limitations - Converted document limitations - Update addComment tool description to explain anchoring limitation - Update resolveComment tool description to explain persistence limitation - Improve readGoogleDoc error messages with detailed API error info
The Google Drive API requires the 'content' field to be present when updating a comment, even when only changing the resolved status. Changes: - Fetch current comment content before updating - Include content in the update request body - Add verification step to check if resolved status was set - Enhance error messages with detailed API error codes This fix resolves the 'Comment content is required' error that occurred when calling resolveComment. Discovered during comprehensive MCP testing after merging PRs a-bonus#1-3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
resolveCommenttool was failing with a "Comment content is required" error when attempting to resolve comments programmatically.Root Cause
The Google Drive API requires the
contentfield to be present in the request body when updating a comment, even when only changing theresolvedstatus. The previous implementation only sent theresolvedfield, causing the API to reject the request.Solution
This PR fixes the issue by:
Changes
resolveCommenttool implementation insrc/server.tsTesting
✅ Verified working through comprehensive MCP testing:
resolveComment- succeeded without errorsBefore This Fix
After This Fix
or (when API doesn't persist the status):
Related
Review Notes