feat(google_docs): create new tools for docs edit #957
+4,563
−439
Conversation
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
…ality - Added `google_docs_edit_text` for unified text editing (insert, delete, replace). - Introduced `google_docs_apply_style` to apply character and paragraph styles in one operation. - Created `google_docs_insert_formatted_text` for inserting markdown-like formatted text. - Enhanced `google_docs_get_document_by_id` to support multiple response formats (raw, plain_text, markdown, structured). - Updated documentation to reflect new tools and usage guidelines.
- Added support for inline code and escape sequences in markdown parsing. - Updated `insert_formatted_text` to handle inline code and escape sequences. - Introduced comprehensive unit tests for various Google Docs tools, including document creation, text editing, and markdown parsing. - Improved test coverage for error handling and response validation across multiple functionalities.
…erage for various functionalities - Deleted the outdated TOOL_DESIGN.md file to streamline documentation. - Improved unit tests for Google Docs tools, including input validation and API call parameters for document creation, text editing, and formatting. - Added tests for new features such as formatted text insertion and style application, ensuring comprehensive coverage of error handling and response validation.
…erage - Moved Google Docs service functions to a dedicated tools package for better organization and maintainability. - Updated test cases to reflect the new import paths for service functions, ensuring all tests remain functional. - Enhanced unit tests for various functionalities, including style application and document creation, to improve overall test coverage and reliability.
- Changed default response format for `get_document_by_id` from 'raw' to 'normalized' for improved consistency. - Updated descriptions in API documentation to reflect new response format options and usage guidelines. - Modified test cases to ensure they validate the new default response format and its structure.
…tation - Changed the description of the default response format from 'raw' to 'normalized' to enhance clarity and maintain backward compatibility.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Related issue
Type of change
How has this been tested?
(Add screenshots or recordings here if applicable.)
Checklist