Please be aware that haven't been following the history of this framework, for that I'm not entirely aware of the impact these changes will have for everyone that depends on it. I tested the fix on our codebase, we're importing the framework using Carthage, the fix was tested on an M1 machine.
All tests for all platforms passed are ✅
Changes:
uses a standard block (instead of convention(block) for printClosure in ConsoleOutputFacility.swift
user a standard block (instead of convention(block) for deserializationClosure in TestBodyDeserializer.swift
through to problems on M1, used Swift Packages (instead of Carthage) for private 3rd party dependencies in the test targets
This PR is a proposal to fix Issue https://github.com/netguru/ResponseDetective/issues/65
Please be aware that haven't been following the history of this framework, for that I'm not entirely aware of the impact these changes will have for everyone that depends on it. I tested the fix on our codebase, we're importing the framework using Carthage, the fix was tested on an M1 machine.
All tests for all platforms passed are ✅
Changes:
convention(block)forprintClosureinConsoleOutputFacility.swiftconvention(block)fordeserializationClosureinTestBodyDeserializer.swiftPlease let me hear your thoughts