Weird new API with exposed disabledDistanceHandlingClasses property

[DivineDominion]

Instead of a method on IQKeyboardManager that hides implementation details users are now encouraged to violate the object's boundaries and mutate one of its properties directly with IQKeyboardManager.sharedManager().disabledDistanceHandlingClasses.addObject(...).

I would understand the other way 'round, but what's the rationale behind this move?

[hackiftekhar]

I exposed those properties because I found it's easy to manage.

[DivineDominion]

On the client side or on the library's?

On 24 May 2016, at 08:27, Mohd Iftekhar Qurashi notifications@github.com wrote:

I exposed those properties because I found it's easy to manage.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

[hackiftekhar]

Both side, but more on the library's side.