-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash During Orphaned Managed Object with Ambiguous KeyPaths #1111
Comments
…n the deletion support. refs #1111
I am not in love with the solution in place here -- it involves allowing an exception to be raised and then capturing it, but I don't see a more elegant solution at the moment. @jeffarena -- we should benchmark this in GateGuru for v3.2 -- the exception may be a performance problem. |
The latest round of changes to the refetching implementation has papered over this issue in GateGuru. Kicking this one to 0.20.1 to focus on non-academic problems. |
Closed by new implementation of refetching support. |
Hey is this fixed because I am getting an error when I am trying to get a user through /user/id.json. the response is laid out like object mapping. Results: { |
Update to the development branch. The change has been merged, but not yet released in a tagged version. |
…n the deletion support. refs RestKit#1111
…e the refreshed visitor implementation. refs RestKit#1111, RestKit#1113
There is a crashing issue due to keyPath ambiguity when working with dynamic mappings and the local object deletion support. The issue goes like this:
is evaluated against a nested keyPath for the mapping that did not match. (
valueForKeyPath:` is invoked with the key path reviews.airport, which raises an exception because the mapped entities don't respect that key path).There are two possible fixes for this:
RKMapperOperationDelegate
methods to track the mappings that are applied to the response and then visiting all of the edges from there.The text was updated successfully, but these errors were encountered: