A modern programming language that makes developers happier.

kotlinlang

How do you solve the issue with the `@Nullable` annotation on the `getActivity()` and `getContext()` in the android SDK 27 changes ? Personally I’m not keen to spread the nullable context all around the app.

Depends on case. `requreActivity()` can be used as easiest solution, equivalent to `getActivity()!!`, but in many cases you actually can check for null activity and do not crash and just do nothing

I, for one, welcome our new non-platform-type overloads