[iOS] Fix compiler error with booleans inside objects #108
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.
Fixes an issue where the iOS generator would generate clients that would fail to compile if they contained a non-nullable boolean inside of an object. At a high-level:
NSNumber *
instead ofBOOL * / NSInteger *
. Required non-nullable booleans/integers are stillBOOL/NSInteger
s.*
types, which don't include that space (f.e.BOOL foo
vs.NSNumber *foo
)strong
andnonnull
modifiers fromBOOL
/NSInteger
types.For more details:
This PR also updates the test suite to test all optional, required and nullable types within an object.
RFPR of: #107