/CoroutineExtension

some custom api and fix bug usage for coroutine 1.3.2

Primary LanguageKotlin

使用JitPack快速依赖

How To


allprojects {
  	repositories {
  		...
  		maven { url 'https://jitpack.io' }
  	}
  }

dependencies {
          implementation 'com.github.mistletoe5215:CoroutineExtension:v1.2.3'
  }

更新

v1.3.0

  • 增加View.acquireObservableScope()获取一个跟随窗口移除时取消的协程域

  • 增加Context.acquireLifecycleScope()从只有context的地方获取一个和lifecycle绑定的协程域，协程block执行完即解绑lifecycle

v1.2.3

  • 打包问题修复revert 使用Jitpack ci 的gradle版本

v1.2.2

  • 增加CustomMainDispatcher，解决1.3.2版本主协程调度器crash问题

v1.2.1

  • 增加FJCoroutineDispatcher调度器FJCoroutineDispatcher,可以与Dispatchers.IO做比较

v1.2.0

  • 对网络请求场景使用超时回收策略调度器MCoroutineDispatcher

  • 删除部分无必要父协程Scope创建

v1.1.0

 data class ResponseDataModel1(
          var code:Int = 0,
          var message:String?=null,
          var data:String?=null
    )

 data class ResponseDataModel2(
          var code:Int = 0,
          var message:String?=null,
          var data:String?=null
    )
 @BaseUrl("www.github.com")
 interface ApiService {
         @GET("getListData")
         fun foo1(@Query param:String):Deferred<ResponseDataModel1>
         @GET("getImageData")
         fun foo2(@Query param:String):Deferred<ResponseDataModel2>
  }
 zip(mService.foo1(param), mService.foo2(param))
                .bindLifecycle(activity)
                .onCompletion {
                    val resultList = it.awaitAll()
                    //ensure get all result
                    if(resultList.size == 2){
                        Log.d("Mistletoe",(resultList[0] as ResponseDataModel1)?.data.toString() +"\n"+
                            (resultList[1] as ResponseDataModel2)?.data.toString()
                        )
                    }
                }.catch {
                    Log.e("Mistletoe",it.message)
                }

v1.0.1

        lifecycleOwner promise{
                //请求接口
                mApiService.foo(param)
           } then {
               mResponseDataModel ->
                //返回结果，更新UI
          } catch { e ->
               //捕获异常并在主线程处理异常
          }

UseAge

使用promise then 实现流式请求

  • 项目使用retrofit v2.6 时
  data class ResponseDataModel(
        var code:Int = 0,
        var message:String?=null,
        var data:String?=null 
  )
@BaseUrl("www.github.com")
 interface ApiService {
  @GET("getListData")
  suspend fun foo(@Query param:String):ResponseDataModel
  }
     lifecycleOwner.promise{
            //请求接口
            mApiService.foo(param)
       }.then({
           mResponseDataModel ->
            //返回结果，更新UI
      }){ e ->
           //捕获异常并处理 
         }
  • 项目使用retrofit v2.3 时
  @BaseUrl("www.github.com")
    interface ApiService {
     @GET("getListData")
     fun foo(@Query param:String):Deferred<ResponseDataModel>
     }
     lifecycleOwner.promise{
            //请求接口
            mApiService.foo(param)
       }.then({
           mResponseDataModel ->
            //返回结果，更新UI
      }){ e ->
           //捕获异常并处理 
         }

使用setTimeOut 执行延时任务

   val handle = setTimeOut(time = 2000L){
         //do delay task
   }
   // cancel task
   handle.cancel()

使用setInterval 执行定时循环周期任务

   val handle = setInterval(Dispatchers.IO, 3000L){
      //do loop task
   }
   // cancel task
   handle.cancel()

使用FlowCountDownTimer实现一个可随时暂停恢复的倒计时

 //实现一个3s的倒计时

 val  mFlowCountDownTimer = FlowCountDownTimer.Builder().from(3)
                 .to(0)
                 .interval(1000L)
                 .withUnit(TimeUnit.SECONDS)
                 .create()
             mFlowCountDownTimer?.apply {
                         watchStart {
                             //观察开始动作
                         }
                         watchCountDown {
                             currentCount ->
                            //观察倒计时
                         }
                         watchComplete {
                            //观察倒计时结束
                         }
                     }?.start()
  //希望暂停时， 
  mFlowCountDownTimer?.pause()
  //希望恢复倒计时时，
  mFlowCountDownTimer?.resume()