Framework for automatic mock generation. Adds a set of handy methods, simplifying testing. One of the best and most complete solutions, including generics support and much more.
There were two issues that cropped up with use of Xcode 16:
Use of .characters on String types. This is now deprecated and we should be calling the functions directly on the Strings
The extensions to Optional for conformance to ExpressibleByStringLiteral etc.
For the first issue, simply removing .characters was enough.
For the second issue, I have just removed the Optional extensions. I think this is safe and will cause little inconvenience to the end user. The change they will need to make is moving from directly passing in "some string" as a parameter to type Parameter<String?> to .value("some string"). This is a direct result of SE-0364.
Description
There were two issues that cropped up with use of Xcode 16:
.characters
on String types. This is now deprecated and we should be calling the functions directly on the StringsExpressibleByStringLiteral
etc.For the first issue, simply removing
.characters
was enough.For the second issue, I have just removed the Optional extensions. I think this is safe and will cause little inconvenience to the end user. The change they will need to make is moving from directly passing in
"some string"
as a parameter to typeParameter<String?>
to.value("some string")
. This is a direct result of SE-0364.Related issue