refactor(OpenAPI): Use proper type inheritance for chat messages #12041
Conversation
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
Member
Author
|
/backport to stable29 |
provokateurin
force-pushed
the
refactor/openapi/chat-message-inheritance
branch
from
a3d11f8 to
790e496
Compare
Signed-off-by: provokateurin <[email protected]>
nickvergessen
force-pushed
the
refactor/openapi/chat-message-inheritance
branch
from
790e496 to
91091e9
Compare
nickvergessen
approved these changes
Apr 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
☑️ Resolves
This makes it a lot easier to handle messages in clients because local and remote messages use the same base type with the same properties.
🛠️ API Checklist
🏁 Checklist
docs/has been updated or is not required