mixing in the ability to send an explicit error from a mock response

[heckj]

for feedback/review:

this is done primarily In order to test error handling - which comes in useful when you're building declarative pipelines that do just that with something like Combine. A recent thread in a closed issue (#24) made me think it might be useful to submit. There aren't any tests yet against this with these changes, but if this looks useful to y'all, I would be happy to create the relevant updates

[ghost]

	Warnings
⚠️	Consider to place some MARK: lines for Sources/Mock.swift, which is over 200 lines big.

	Messages
📖	View more details on Bitrise
📖	Mocker: Executed 18 tests, with 0 failures (0 unexpected) in 1.690 (1.754) seconds

Mocker.framework: Coverage: 89.02

File	Coverage
MockingURLProtocol.swift	86.27%	✅
Mock.swift	84.62%	✅

Generated by 🚫 Danger Swift against 56c30a4

[AvdLee]

@heckj thanks for your contribution! I'd love to adjust the code a bit, update the documentation and add some tests. If you would be able to add that, we can merge this in!

[heckj]

I can definitely do that - might be a few days, but hopefully not as long as the first wait ;-)

[github-actions]

This PR is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days.

[heckj]

👋 @AvdLee - I updated this PR a while ago, so I think it's just waiting on your approval for anything further.

[AvdLee]

Thanks, this looks great! Sorry for not coming back to this any earlier. I think it slipped through somehow!

[ghost]

Congratulations! 🎉 This was released as part of Release 2.2.0 🚀

Generated by GitBuddy