openapi-operations

What problem does it solve?

Establishes consistent OpenAPI operation naming, pagination, and response patterns to prevent ambiguous or conflicting API specs and to streamline client generation.

Core Features & Use Cases

• Enforces that operationId is fully descriptive while x-method-name omits the tag, preventing naming leakage.
• Mandates pagination for list operations using core parameters and linked headers, ensuring standard client navigation.
• Validates response code usage (only 200/201) to align with framework error handling and reduce boilerplate.
• Use Case: A team migrating an API to OpenAPI 3.x can apply these rules to ensure clean, consistent, and machine-friendly specifications.

Quick Start

Update your OpenAPI specifications to enforce Rule 11-13 by standardizing operationId and x-method-name, applying mandatory pagination, and restricting responses to 200/201.