-
Notifications
You must be signed in to change notification settings - Fork 383
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
Backend: update openapi spec #897
Conversation
|
338b460
to
cab2648
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #897 +/- ##
==========================================
+ Coverage 76.64% 76.72% +0.08%
==========================================
Files 259 272 +13
Lines 10583 10620 +37
==========================================
+ Hits 8111 8148 +37
Misses 2472 2472 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks, Eric
…s generated by router tags
fd7bb91
to
cbd0ac7
Compare
Description
Working towards having the OpenAPI Spec file being code driven and generated via FastAPI. This requires all path parameters, query parameters, and schemas used for requests and responses to have the additional metadata added to each field.
In the process, also trying to DRY up some of the path parameters, query parameters, and schemas used throughout the API by using inheritance and abstraction.
Docstrings in the Routers are also being cleaned up because this docstrings are using by FastAPI to document each endpoint in the OpenAPI Spec.
AI Description
The PR introduces several new features and improvements to the backend of a web application, primarily focusing on the addition of new features and improvements to existing ones.
New Features
/tool/auth
endpoint for tool authentication, which is different from the regular login OAuth flow. It stores aToolAuth
object in the database containing the access token for the tool./v1/agents
endpoint for managing agents. It allows creating, listing, updating, and deleting agents, as well as managing agent tool metadata./v1/chat
endpoint for handling chat requests. It supports streaming chat responses, regenerating chat streams, and non-streamed chat responses./v1/conversations
endpoint for managing conversations. It allows creating, listing, updating, and deleting conversations, as well as uploading and listing files, generating titles, and synthesizing messages./v1/deployments
endpoint for managing deployments. It supports creating, listing, updating, and deleting deployments, as well as setting environment variables./v1/experimental_features
endpoint for listing experimental features and their enabled state./v1/models
endpoint for managing models. It allows <co: 8>creating, listing, updating, and deleting models.</co: