Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Reason: mutableOrderedSetValueForKey and mutableSetValueForKey now re… #122

Merged
merged 1 commit into from
Jan 10, 2017
Merged

Reason: mutableOrderedSetValueForKey and mutableSetValueForKey now re… #122

merged 1 commit into from
Jan 10, 2017

Commits on Nov 29, 2016

  1. Reason: mutableOrderedSetValueForKey and mutableSetValueForKey now re… 

    …turns a proxy set and therefore the returned value is not a backing storage and therefore all the calls that tries to add object are forwarded it to backing storage, while setValue:forKey: will set it to an empty set

Solution: Adding the values to a real set and setting that in setValue:forKey:
    @monishsyed
    monishsyed committed Nov 29, 2016
    Configuration menu
    Copy the full SHA
    6841e78 View commit details
    Browse the repository at this point in the history