fix: keep escaping closure attribute in mocks #71
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.
Up until this point, all attributes including
@escaping
were removed from function parameter types in the generated mock implementation to allow using them in other places than parameter positions. (ex.: enum cases)This however is wrong when generating the producer resolver, that uses the function parameter types at closure parameter positions and needs to mark potential closure type parameters
@escaping
.Also,
inout
was previously removed from closure parameters in the above process. This PR keeps it and adds support forinout
types inwillProduce
clauses.