chore: Ensure status code annotation is unique for get reminders - #17640
Merged
nickvergessen merged 1 commit intoApr 6, 2026
Merged
Conversation
SystemKeeper
added
bug
feature: chat 💬
Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>
SystemKeeper
force-pushed
the
chore/noid/adjust-returncode-comment-on-reminder
branch
from
April 6, 2026 16:56
d11f7ab to
8d252a9
Compare
Antreesy
approved these changes
Apr 6, 2026
nickvergessen
approved these changes
Apr 6, 2026
nickvergessen
deleted the
chore/noid/adjust-returncode-comment-on-reminder
branch
April 6, 2026 18:21
Member
|
/backport to stable33 |
Member
|
/backport to stable32 |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When multiple return codes are set in the annotation, only the last one will end up in the openapi file:
After:
I am not sure if the openapi generation for typescript is correct, was it just not updated or something wrong on my end? @AntreesyOutdated composer packages it seems, sorry.