You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output models should be generated with non-optional Swift properties for members having the @required trait.
Models should continue to be optional under the hood / in private Swift properties. Presence of required members should be checked during deserialization, and then force-unwrapped by a public accessor when the customer accesses the member.
There should be a mechanism for Trebuchet to identify a breaking API change related to the required trait, and the SDK will major version that service as needed.
Models that are used as both input and output may have non-optional getters; this is okay since customers should not use getters when preparing a request for input.
Use Case
To make best use of Swift language features by exposing required members as non-optional.
Proposed Solution
No response
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
The text was updated successfully, but these errors were encountered:
Describe the feature
Output models should be generated with non-optional Swift properties for members having the
@required
trait.Use Case
To make best use of Swift language features by exposing required members as non-optional.
Proposed Solution
No response
Other Information
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: