Refactor Tool Parameter Schemas #110
Merged
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
- Remove max(80) constraint from description fields\n- Restructure browseMessage parameters to flatten the action object\n- Simplify parameter validation logic\n- Improve error handling\n- Fix linting error by removing unused parameter
|
🎉 This PR is included in version mycoder-agent-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version mycoder-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refactor Tool Parameter Schemas
This PR addresses issue #109 by improving the tool parameter schemas in several components:
Changes
Removed
.max(80)constraint from description fields in multiple tools:Significant restructuring of parameter schema in browseMessage.ts:
Benefits
Testing
All tests are passing with these changes, confirming backward compatibility while improving the code structure.
Notes
The description fields still maintain the documentation stating "(max 80 chars)" to guide users, but the hard validation constraint has been removed to allow for more flexibility.