[DEVTOOLING-1076] Fixing iOS SDK #47
Merged
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
carnellj-genesys
approved these changes
Mar 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Platform API iOS SDK was not generated properly - due to two swagger annotations generating incorrect Swift code.
“entries” attribute in “CsvUploadPreviewResponse” model (array of arrays of strings) not interpreted properly by the openapi-generator and related templates
“Range” model used as the attribute’s type of another model. “Range” is a reserved keyword in Swift. The class name is properly transformed to “ModelRange” in Swift. But attributes (e.g. in “Reoccurrence” model) continue to reference Range class.