Skip to content
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

bug: the openapi schema is missing 85% of response types #4738

Open
sneko opened this issue Jun 13, 2024 · 1 comment
Open

bug: the openapi schema is missing 85% of response types #4738

sneko opened this issue Jun 13, 2024 · 1 comment
Labels
bug managed on taiga This issue has been moved to our project at Taiga.io

Comments

@sneko
Copy link

sneko commented Jun 13, 2024

Steps To Reproduce

Expected behavior

To have all response schemas so generating clients would match the true payload returned.

Actual behavior

Currently over 75 endpoints, only 11 have their response schema declared. So for the rest it'sconsidering there is no response payload. Which is problematic for typings... but also to develop efficiently.

This is a bit strange because from what I understand the openapi.json is automatically generated from Clojure models?

Screenshots or video

No response

Desktop (please complete the following information)

No response

Smartphone (please complete the following information)

No response

Environment (please complete the following information)

No response

Frontend Stack Trace

No response

Backend Stack Trace

No response

Additional context

No response

cc @niwinz

@sneko sneko added the bug label Jun 13, 2024
@madalenapmelo-kp madalenapmelo-kp added the managed on taiga This issue has been moved to our project at Taiga.io label Jun 19, 2024
@madalenapmelo-kp
Copy link
Contributor

Hi @sneko,

Thanks for reporting this! I've created an issue on Taiga so that we can look into this, you can find it here: https://tree.taiga.io/project/penpot/issue/8129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug managed on taiga This issue has been moved to our project at Taiga.io
Projects
None yet
Development

No branches or pull requests

2 participants