Hi everyone,
I’ve encountered a peculiar issue with Strapi’s automatically generated Swagger (OpenAPI) documentation. The documentation provides a basic overview of the API endpoints, but it significantly lacks in detailing the model schema configurations. Attributes such as **editable, default value, label, **and sort options, crucial for a comprehensive understanding and effective use of the API, are missing in the Swagger output. What makes this particularly strange is that these attributes can be defined within the Strapi admin panel (frontend), yet they don’t appear in the generated schema documentation.
This gap in the documentation makes it difficult for API consumers to grasp the full capabilities and constraints, potentially leading to confusion or misuse. Has anyone else experienced this issue or have suggestions on how to ensure these important details are included in the Swagger documentation?
This topic has been created from a Discord post (1222265175088955562) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord