fix: [OpenAPI] String properties are not mistakenly generated as File anymore - #1260
Merged
Conversation
CharlesDuboisSAP
added
please merge
Jonas-Isr
previously approved these changes
Aug 25, 2026
Jonas-Isr
left a comment
Jonas-Isr
left a comment
Member
There was a problem hiding this comment.
Looks good to me :)
As discussed, we can investigate this issue a bit further in the near future but this looks like a good fix to the initial problem.
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.
Context
A property of type String can be either a File or a strong depending on the content type
Feature scope:
Definition of Done
Error handling created / updated & covered by the tests aboveDocumentation updated