1.0.0-beta1

Uses new modular packages. You can now just include what you need without databinding or support library coming in for free! The new system has the following modules:

• k4kotlin-core : Contains extensions without any other support lib dependency
• k4kotlin-androidx : Contains extensions that uses support lib dependency from jetpack
• k4kotlin-databinding : Contains extensions for android databinding library
• k4kotlin-retrofit : Same as before

Note: The library now uses androidx naming packages for androidx package and sample app

Your feedback is welcome to hit the stable.

0.6.0

• Updated Gradle wrapper
• Updated kotlin version to 1.3.0 and migrated coroutines to stable version

0.5.4

• Make logs extension functions inline to reduce method call overheads

0.5.3

Core module:

• New getColorStateListCompat extension (Thanks to @olivierperez )
• toggle method for MutableCollection which adds an element if not already present else removes it

Check out Wiki for more details.

0.5.2

Fix onUnsuccessfulResponseOrFailureNotCancelled method

0.5.1

onUnsuccessfulResponse, onUnsuccessfulResponseOrFailure and onUnsuccessfulResponseOrFailureNotCancelled methods for handling unsuccessful responses other that 2xx.

0.5.0

New:

Retrofit Coroutines Support:

• enqueueAwait, enqueueDeferred, enqueueDeferredResponse methods. You can find more in the Wiki

Toast and ToastQueue Support:

• 'toast' method for activity and fragment
• 'toastNow' method for dismissing all previous toasts and show the new toast

0.4.2

Fix previous release

0.4.1

Fix: Retrofit's empty callbacks

0.4.0

New:

• New RetrofitCallback class to easily handle multiple types of responses.
• For example,
  • It handles onCompleted callback for onResponse and onFailure.
  • Callbacks for particular group of codes are returned as response like 2xx, 3xx, 4xx & 5xx.
  • Callbacks for any particular callback for all the http response codes
  • Specific failure handling case when call is not cancelled.
  • Callback when call is cancelled by the user (developer to be precise)
• You can attach a progressView to the callback which will handle showing and hiding of a view when a call is completed
• There is also a lazyProgressView which will hide itself when call is finished. Showing a view should be handled by the developer

Changes: Retrofit enqueue now accepts any object implementing lifecycle owner to limit call to its lifecycle