* Basic setup for drf-spectacular * Updated to only handle /api/v1 endpoints * feat: add asset and user endpoints with URL routing - Introduced new asset-related endpoints for user assets and server assets, allowing for asset uploads and management. - Added user endpoint to retrieve current user information. - Updated URL routing to include new asset and user patterns. - Enhanced issue handling with a new search endpoint for issues across multiple fields. - Expanded member management with a new endpoint for workspace members. * Group endpoints by tags * Detailed schema definitions and examples for asset endpoints * Removed unnecessary extension * Specify avatar_url field separately * chore: add project docs * chore: correct all errors * chore: added open spec in work items * feat: enhance cycle API endpoints with detailed OpenAPI specifications - Updated CycleAPIEndpoint and CycleIssueAPIEndpoint to include detailed OpenAPI schema definitions for GET, POST, PATCH, and DELETE operations. - Specified allowed HTTP methods for each endpoint in the URL routing. - Improved documentation for cycle creation, updating, and deletion, including request and response examples. * chore: added open spec in labels * chore: work item properties * feat: enhance API endpoints with OpenAPI specifications and HTTP method definitions - Added detailed OpenAPI schema definitions for various API endpoints including Intake, Module, and State. - Specified allowed HTTP methods for each endpoint in the URL routing for better clarity and documentation. - Improved request and response examples for better understanding of API usage. - Introduced unarchive functionality for cycles and modules with appropriate endpoint definitions. * chore: run formatter * Removed unnecessary settings for authentication * Refactors OpenAPI documentation structure Improves the organization and maintainability of the OpenAPI documentation by modularizing the `openapi_spec_helpers.py` file. The changes include: - Migrates common parameters, responses, examples, and authentication extensions to separate modules. - Introduces helper decorators for different endpoint types. - Updates view imports to use the new module paths. - Removes the legacy `openapi_spec_helpers.py` file. This refactoring results in a more structured and easier-to-maintain OpenAPI documentation setup. * Refactor OpenAPI endpoint specifications - Removed unnecessary parameters from the OpenAPI documentation for various endpoints in the asset, cycle, and project views. - Updated request structures to improve clarity and consistency across the API documentation. - Enhanced response formatting for better readability and maintainability. * Enhance API documentation with detailed endpoint descriptions Updated various API endpoints across the application to include comprehensive docstrings that clarify their functionality. Each endpoint now features a summary and detailed description, improving the overall understanding of their purpose and usage. This change enhances the OpenAPI specifications for better developer experience and documentation clarity. * Enhance API serializers and views with new request structures - Added new serializers for handling cycle and module issue requests, including `CycleIssueRequestSerializer`, `TransferCycleIssueRequestSerializer`, `ModuleIssueRequestSerializer`, and intake issue creation/updating serializers. - Updated existing serializers to improve clarity and maintainability, including the `UserAssetUploadSerializer` and `IssueAttachmentUploadSerializer`. - Refactored API views to utilize the new serializers, enhancing the request handling for cycle and intake issue endpoints. - Improved OpenAPI documentation by replacing inline request definitions with serializer references for better consistency and readability. * Refactor OpenAPI documentation and endpoint specifications - Replaced inline schema definitions with dedicated decorators for various endpoint types, enhancing clarity and maintainability. - Updated API views to utilize new decorators for user, cycle, intake, module, and project endpoints, improving consistency in OpenAPI documentation. - Removed unnecessary parameters and responses from endpoint specifications, streamlining the documentation for better readability. - Enhanced the organization of OpenAPI documentation by modularizing endpoint-specific decorators and parameters. * chore: correct formatting * chore: correct formatting for all api folder files * refactor: clean up serializer imports and test setup - Removed unused `StateLiteSerializer` import from the serializer module. - Updated test setup to include a noqa comment for the `django_db_setup` fixture, ensuring clarity in the code. - Added missing commas in user data dictionary for consistency. * feat: add project creation and update serializers with validation - Introduced `ProjectCreateSerializer` and `ProjectUpdateSerializer` to handle project creation and updates, respectively. - Implemented validation to ensure project leads and default assignees are members of the workspace. - Updated API views to utilize the new serializers for creating and updating projects, enhancing request handling. - Added OpenAPI documentation references for the new serializers in the project API endpoints. * feat: update serializers to include additional read-only fields * refactor: rename intake issue serializers and enhance structure - Renamed `CreateIntakeIssueRequestSerializer` to `IntakeIssueCreateSerializer` and `UpdateIntakeIssueRequestSerializer` to `IntakeIssueUpdateSerializer` for clarity. - Introduced `IssueSerializer` for nested issue data in intake requests, improving the organization of serializer logic. - Updated API views to utilize the new serializer names, ensuring consistency across the codebase. * refactor: rename issue serializer for intake and enhance API documentation - Renamed `IssueSerializer` to `IssueForIntakeSerializer` for better clarity in the context of intake issues. - Updated references in `IntakeIssueCreateSerializer` and `IntakeIssueUpdateSerializer` to use the new `IssueForIntakeSerializer`. - Added OpenAPI documentation for the `get_workspace_work_item` endpoint, detailing parameters and responses for improved clarity. * chore: modules and cycles serializers * feat: add new serializers for label and issue link management - Introduced `LabelCreateUpdateSerializer`, `IssueLinkCreateSerializer`, `IssueLinkUpdateSerializer`, and `IssueCommentCreateSerializer` to enhance the handling of label and issue link data. - Updated existing API views to utilize the new serializers for creating and updating labels, issue links, and comments, improving request handling and validation. - Added `IssueSearchSerializer` for searching issues, streamlining the search functionality in the API. * Don't consider read only fields as required * Add setting to separate request and response definitions * Fixed avatar_url warning on openapi spec generation * Made spectacular disabled by default * Moved spectacular settings into separate file and added detailed descriptions to tags * Specify methods for asset urls * Better server names * Enhance API documentation with summaries for various endpoints - Added summary descriptions for user asset, cycle, intake, issue, member, module, project, state, and user API endpoints to improve clarity and usability of the API documentation. - Updated the OpenAPI specifications to reflect these changes, ensuring better understanding for developers interacting with the API. * Add contact information to OpenAPI settings - Included contact details for Plane in the OpenAPI settings to enhance API documentation and provide developers with a direct point of contact for support. - This addition aims to improve the overall usability and accessibility of the API documentation. * Reordered tags and improved description relavancy * Enhance OpenAPI documentation for cycle and issue endpoints - Added response definitions for the `get_cycle_issues` and `delete_cycle_issue` methods in the CycleIssueAPIEndpoint to clarify expected outcomes. - Included additional response codes for the IssueSearchEndpoint to handle various error scenarios, improving the overall API documentation and usability. * Enhance serializer documentation across multiple files - Updated docstrings for various serializers including UserAssetUploadSerializer, AssetUpdateSerializer, and others to provide clearer descriptions of their functionality and usage. - Improved consistency in formatting and language across serializer classes to enhance readability and maintainability. - Added detailed explanations for new serializers related to project, module, and cycle management, ensuring comprehensive documentation for developers. * Refactor API endpoints for cycles, intake, modules, projects, and states - Replaced existing API endpoint classes with more descriptive names such as CycleListCreateAPIEndpoint, CycleDetailAPIEndpoint, IntakeIssueListCreateAPIEndpoint, and others to enhance clarity. - Updated URL patterns to reflect the new endpoint names, ensuring consistency across the API. - Improved documentation and method summaries for better understanding of endpoint functionalities. - Enhanced query handling in the new endpoint classes to streamline data retrieval and improve performance. * Refactor issue and label API endpoints for clarity and functionality - Renamed existing API endpoint classes to more descriptive names such as IssueListCreateAPIEndpoint, IssueDetailAPIEndpoint, LabelListCreateAPIEndpoint, and LabelDetailAPIEndpoint to enhance clarity. - Updated URL patterns to reflect the new endpoint names, ensuring consistency across the API. - Improved method summaries and documentation for better understanding of endpoint functionalities. - Streamlined query handling in the new endpoint classes to enhance data retrieval and performance. * Refactor asset API endpoint methods and introduce new status enums - Updated the GenericAssetEndpoint to only allow POST requests for asset creation, removing the GET method. - Modified the get method to require asset_id, ensuring that asset retrieval is always tied to a specific asset. - Added new IntakeIssueStatus and ModuleStatus enums to improve clarity and management of asset and module states. - Enhanced OpenAPI settings to include these new enums for better documentation and usability. * enforce naming convention * Added LICENSE to openapi spec * Enhance OpenAPI documentation for various API endpoints - Updated API endpoints in asset, cycle, intake, issue, module, project, and state views to include OpenApiRequest and OpenApiExample for better request documentation. - Added example requests for creating and updating resources, improving clarity for API consumers. - Ensured consistent use of OpenApi utilities across all relevant endpoints to enhance overall API documentation quality. * Enhance OpenAPI documentation for various API endpoints - Added detailed descriptions to multiple API endpoints across asset, cycle, intake, issue, module, project, state, and user views to improve clarity for API consumers. - Ensured consistent documentation practices by including descriptions that outline the purpose and functionality of each endpoint. - This update aims to enhance the overall usability and understanding of the API documentation. * Update OpenAPI examples and enhance project queryset logic - Changed example fields in OpenAPI documentation for issue comments from "content" to "comment_html" to reflect the correct structure. - Introduced a new `get_queryset` method in the ProjectDetailAPIEndpoint to filter projects based on user membership and workspace, while also annotating additional project-related data such as total members, cycles, and modules. - Updated permission checks to use the correct attribute name for project identifiers, ensuring accurate permission handling. * Enhance OpenAPI documentation and add response examples - Updated multiple API endpoints across asset, cycle, intake, issue, module, project, state, and user views to include new OpenApiResponse examples for better clarity on expected outcomes. - Introduced new parameters for project and issue identifiers to improve request handling and documentation consistency. - Enhanced existing responses with detailed examples to aid API consumers in understanding the expected data structure and error handling. - This update aims to improve the overall usability and clarity of the API documentation. * refactor: update terminology from 'issues' to 'work items' across multiple API endpoints for consistency and clarity * use common timezones from pytz for choices * Moved the openapi utils to the new folder structure * Added exception logging in GenericAssetEndpoint to improve error handling * Fixed code rabbit suggestions * Refactored IssueDetailAPIEndpoint to streamline issue retrieval and response handling, removing redundant external ID checks and custom ordering logic. --------- Co-authored-by: pablohashescobar <nikhilschacko@gmail.com> Co-authored-by: NarayanBavisetti <narayan3119@gmail.com>
272 lines
13 KiB
Python
272 lines
13 KiB
Python
"""
|
|
OpenAPI/Swagger configuration for drf-spectacular.
|
|
|
|
This file contains the complete configuration for API documentation generation.
|
|
"""
|
|
|
|
SPECTACULAR_SETTINGS = {
|
|
# ========================================================================
|
|
# Basic API Information
|
|
# ========================================================================
|
|
"TITLE": "The Plane REST API",
|
|
"DESCRIPTION": (
|
|
"The Plane REST API\n\n"
|
|
"Visit our quick start guide and full API documentation at "
|
|
"[developers.plane.so](https://developers.plane.so/api-reference/introduction)."
|
|
),
|
|
"CONTACT": {
|
|
"name": "Plane",
|
|
"url": "https://plane.so",
|
|
"email": "support@plane.so",
|
|
},
|
|
"VERSION": "0.0.1",
|
|
"LICENSE": {
|
|
"name": "GNU AGPLv3",
|
|
"url": "https://github.com/makeplane/plane/blob/preview/LICENSE.txt",
|
|
},
|
|
# ========================================================================
|
|
# Schema Generation Settings
|
|
# ========================================================================
|
|
"SERVE_INCLUDE_SCHEMA": False,
|
|
"SCHEMA_PATH_PREFIX": "/api/v1/",
|
|
"SCHEMA_CACHE_TIMEOUT": 0, # disables caching
|
|
# ========================================================================
|
|
# Processing Hooks
|
|
# ========================================================================
|
|
"PREPROCESSING_HOOKS": [
|
|
"plane.utils.openapi.hooks.preprocess_filter_api_v1_paths",
|
|
],
|
|
# ========================================================================
|
|
# Server Configuration
|
|
# ========================================================================
|
|
"SERVERS": [
|
|
{"url": "http://localhost:8000", "description": "Local"},
|
|
{"url": "https://api.plane.so", "description": "Production"},
|
|
],
|
|
# ========================================================================
|
|
# API Tag Definitions
|
|
# ========================================================================
|
|
"TAGS": [
|
|
# System Features
|
|
{
|
|
"name": "Assets",
|
|
"description": (
|
|
"**File Upload & Presigned URLs**\n\n"
|
|
"Generate presigned URLs for direct file uploads to cloud storage. Handle user avatars, "
|
|
"cover images, and generic project assets with secure upload workflows.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Generate presigned URLs for S3 uploads\n"
|
|
"- Support for user avatars and cover images\n"
|
|
"- Generic asset upload for projects\n"
|
|
"- File validation and size limits\n\n"
|
|
"*Use Cases:* User profile images, project file uploads, secure direct-to-cloud uploads."
|
|
),
|
|
},
|
|
# Project Organization
|
|
{
|
|
"name": "Cycles",
|
|
"description": (
|
|
"**Sprint & Development Cycles**\n\n"
|
|
"Create and manage development cycles (sprints) to organize work into time-boxed iterations. "
|
|
"Track progress, assign work items, and monitor team velocity.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create and configure development cycles\n"
|
|
"- Assign work items to cycles\n"
|
|
"- Track cycle progress and completion\n"
|
|
"- Generate cycle analytics and reports\n\n"
|
|
"*Use Cases:* Sprint planning, iterative development, progress tracking, team velocity."
|
|
),
|
|
},
|
|
# System Features
|
|
{
|
|
"name": "Intake",
|
|
"description": (
|
|
"**Work Item Intake Queue**\n\n"
|
|
"Manage incoming work items through a dedicated intake queue for triage and review. "
|
|
"Submit, update, and process work items before they enter the main project workflow.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Submit work items to intake queue\n"
|
|
"- Review and triage incoming work items\n"
|
|
"- Update intake work item status and properties\n"
|
|
"- Accept, reject, or modify work items before approval\n\n"
|
|
"*Use Cases:* Work item triage, external submissions, quality review, approval workflows."
|
|
),
|
|
},
|
|
# Project Organization
|
|
{
|
|
"name": "Labels",
|
|
"description": (
|
|
"**Labels & Tags**\n\n"
|
|
"Create and manage labels to categorize and organize work items. Use color-coded labels "
|
|
"for easy identification, filtering, and project organization.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create custom labels with colors and descriptions\n"
|
|
"- Apply labels to work items for categorization\n"
|
|
"- Filter and search by labels\n"
|
|
"- Organize labels across projects\n\n"
|
|
"*Use Cases:* Priority marking, feature categorization, bug classification, team organization."
|
|
),
|
|
},
|
|
# Team & User Management
|
|
{
|
|
"name": "Members",
|
|
"description": (
|
|
"**Team Member Management**\n\n"
|
|
"Manage team members, roles, and permissions within projects and workspaces. "
|
|
"Control access levels and track member participation.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Invite and manage team members\n"
|
|
"- Assign roles and permissions\n"
|
|
"- Control project and workspace access\n"
|
|
"- Track member activity and participation\n\n"
|
|
"*Use Cases:* Team setup, access control, role management, collaboration."
|
|
),
|
|
},
|
|
# Project Organization
|
|
{
|
|
"name": "Modules",
|
|
"description": (
|
|
"**Feature Modules**\n\n"
|
|
"Group related work items into modules for better organization and tracking. "
|
|
"Plan features, track progress, and manage deliverables at a higher level.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create and organize feature modules\n"
|
|
"- Group work items by module\n"
|
|
"- Track module progress and completion\n"
|
|
"- Manage module leads and assignments\n\n"
|
|
"*Use Cases:* Feature planning, release organization, progress tracking, team coordination."
|
|
),
|
|
},
|
|
# Core Project Management
|
|
{
|
|
"name": "Projects",
|
|
"description": (
|
|
"**Project Management**\n\n"
|
|
"Create and manage projects to organize your development work. Configure project settings, "
|
|
"manage team access, and control project visibility.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create, update, and delete projects\n"
|
|
"- Configure project settings and preferences\n"
|
|
"- Manage team access and permissions\n"
|
|
"- Control project visibility and sharing\n\n"
|
|
"*Use Cases:* Project setup, team collaboration, access control, project configuration."
|
|
),
|
|
},
|
|
# Project Organization
|
|
{
|
|
"name": "States",
|
|
"description": (
|
|
"**Workflow States**\n\n"
|
|
"Define custom workflow states for work items to match your team's process. "
|
|
"Configure state transitions and track work item progress through different stages.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create custom workflow states\n"
|
|
"- Configure state transitions and rules\n"
|
|
"- Track work item progress through states\n"
|
|
"- Set state-based permissions and automation\n\n"
|
|
"*Use Cases:* Custom workflows, status tracking, process automation, progress monitoring."
|
|
),
|
|
},
|
|
# Team & User Management
|
|
{
|
|
"name": "Users",
|
|
"description": (
|
|
"**Current User Information**\n\n"
|
|
"Get information about the currently authenticated user including profile details "
|
|
"and account settings.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Retrieve current user profile\n"
|
|
"- Access user account information\n"
|
|
"- View user preferences and settings\n"
|
|
"- Get authentication context\n\n"
|
|
"*Use Cases:* Profile display, user context, account information, authentication status."
|
|
),
|
|
},
|
|
# Work Item Management
|
|
{
|
|
"name": "Work Item Activity",
|
|
"description": (
|
|
"**Activity History & Search**\n\n"
|
|
"View activity history and search for work items across the workspace. "
|
|
"Get detailed activity logs and find work items using text search.\n\n"
|
|
"*Key Features:*\n"
|
|
"- View work item activity history\n"
|
|
"- Search work items across workspace\n"
|
|
"- Track changes and modifications\n"
|
|
"- Filter search results by project\n\n"
|
|
"*Use Cases:* Activity tracking, work item discovery, change history, workspace search."
|
|
),
|
|
},
|
|
{
|
|
"name": "Work Item Attachments",
|
|
"description": (
|
|
"**Work Item File Attachments**\n\n"
|
|
"Generate presigned URLs for uploading files directly to specific work items. "
|
|
"Upload and manage attachments associated with work items.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Generate presigned URLs for work item attachments\n"
|
|
"- Upload files directly to work items\n"
|
|
"- Retrieve and manage attachment metadata\n"
|
|
"- Delete attachments from work items\n\n"
|
|
"*Use Cases:* Screenshots, error logs, design files, supporting documents."
|
|
),
|
|
},
|
|
{
|
|
"name": "Work Item Comments",
|
|
"description": (
|
|
"**Comments & Discussions**\n\n"
|
|
"Add comments and discussions to work items for team collaboration. "
|
|
"Support threaded conversations, mentions, and rich text formatting.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Add comments to work items\n"
|
|
"- Thread conversations and replies\n"
|
|
"- Mention users and trigger notifications\n"
|
|
"- Rich text and markdown support\n\n"
|
|
"*Use Cases:* Team discussions, progress updates, code reviews, decision tracking."
|
|
),
|
|
},
|
|
{
|
|
"name": "Work Item Links",
|
|
"description": (
|
|
"**External Links & References**\n\n"
|
|
"Link work items to external resources like documentation, repositories, or design files. "
|
|
"Maintain connections between work items and external systems.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Add external URL links to work items\n"
|
|
"- Validate and preview linked resources\n"
|
|
"- Organize links by type and category\n"
|
|
"- Track link usage and access\n\n"
|
|
"*Use Cases:* Documentation links, repository connections, design references, external tools."
|
|
),
|
|
},
|
|
{
|
|
"name": "Work Items",
|
|
"description": (
|
|
"**Work Items & Tasks**\n\n"
|
|
"Create and manage work items like tasks, bugs, features, and user stories. "
|
|
"The core entities for tracking work in your projects.\n\n"
|
|
"*Key Features:*\n"
|
|
"- Create, update, and manage work items\n"
|
|
"- Assign to team members and set priorities\n"
|
|
"- Track progress through workflow states\n"
|
|
"- Set due dates, estimates, and relationships\n\n"
|
|
"*Use Cases:* Bug tracking, task management, feature development, sprint planning."
|
|
),
|
|
},
|
|
],
|
|
# ========================================================================
|
|
# Security & Authentication
|
|
# ========================================================================
|
|
"AUTHENTICATION_WHITELIST": [
|
|
"plane.api.middleware.api_authentication.APIKeyAuthentication",
|
|
],
|
|
# ========================================================================
|
|
# Schema Generation Options
|
|
# ========================================================================
|
|
"COMPONENT_NO_READ_ONLY_REQUIRED": True,
|
|
"COMPONENT_SPLIT_REQUEST": True,
|
|
"ENUM_NAME_OVERRIDES": {
|
|
"ModuleStatusEnum": "plane.db.models.module.ModuleStatus",
|
|
"IntakeWorkItemStatusEnum": "plane.db.models.intake.IntakeIssueStatus",
|
|
},
|
|
}
|