Implement smarter KVC handling for class fakes #357
Merged
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.
This is an attempt at addressing #355. I have confirmed with @pivotal-tom-mcneely that this patch does address the situation that prompted him to file the issue.
I tried not make the KVC implementation too smart. The
-valueForKey:
implementation won't try to call into any other stubbed methods to retrieve a value for return. The main goal was to ensure that calling-valueForKey:
won't simply throw an exception in cases where a real instance of the class wouldn't.