-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Add Comment Blocks for Multi-Agent API Endpoints #18
Merged
Conversation
This file contains 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
Fr4nc3
commented
Jan 2, 2025
Roopan-Microsoft
requested changes
Jan 3, 2025
Roopan-Microsoft
approved these changes
Jan 8, 2025
🎉 This PR is included in version 1.1.0 🎉 The release is available on GitHub release 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.
Purpose
This PR adds detailed Swagger-style comment blocks for all key endpoints in the Multi-Agent API. These changes enhance the API's documentation by specifying parameters, request/response schemas, and descriptions for each endpoint, making the API more accessible and easier to use for developers and integrators.
Does this introduce a breaking change?
How to Test
/docs
or/swagger
).What to Check
Verify that the following are valid:
/input_task
/human_feedback
/human_clarification_on_plan
/approve_step_or_steps
/plans
/steps/{plan_id}
/agent_messages/{session_id}
/messages
(GET and DELETE)/api/agent-tools
Other Information
These changes are intended to improve developer experience and API usability. They do not modify the API's underlying functionality or introduce breaking changes.