Skip to content

fix(API): Comment creation schema fix #STRINGS-866#718

Merged
jablan merged 2 commits intomasterfrom
866-fix-comments-creation-schema
Nov 20, 2024
Merged

fix(API): Comment creation schema fix #STRINGS-866#718
jablan merged 2 commits intomasterfrom
866-fix-comments-creation-schema

Conversation

@jablan
Copy link
Copy Markdown
Collaborator

@jablan jablan commented Nov 20, 2024

@theSoenke
Copy link
Copy Markdown
Collaborator

jablan i believe for this endpoint it's specifically an issue because it passes an array via query params. Are there by any chance more endpoints with similar issues? 😅 And does it have an impact on the client interfaces?

@jablan
Copy link
Copy Markdown
Collaborator Author

jablan commented Nov 20, 2024

Sönke Behrendt (@theSoenke) I searched quickly through all create endpoints and couldn't find another where an array is specified in query params.

yeah, this impacts the client interfaces, but I'm not sure what we could do instead. this was a bug in schema description.

@theSoenke
Copy link
Copy Markdown
Collaborator

jablan thanks for checking. Yeah, then this have to be a breaking change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants