Kotlin way of building RecyclerView Adapter 🧩. You do not have to write RecyclerView Adapters again and again and suffer from handling of different view types. Kiel will help you.

@ibrahimyilmaz If the RecyclerView layout uses wrap_content instead of match_parent and setHasFixedSize = true, the list will not be displayed.

activity_country_indonesia.xml

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:orientation="vertical">

    <com.google.android.material.appbar.AppBarLayout
        android:id="@+id/app_bar_layout"
        android:layout_width="match_parent"
        android:layout_height="wrap_content">

        <androidx.appcompat.widget.Toolbar
            android:id="@+id/toolbar"
            android:layout_width="match_parent"
            android:layout_height="wrap_content" />

    </com.google.android.material.appbar.AppBarLayout>

    <androidx.recyclerview.widget.RecyclerView
        android:id="@+id/recycler_view"
        android:layout_width="match_parent"
        android:layout_height="match_parent" / "wrap_content"
        app:layoutManager="androidx.recyclerview.widget.LinearLayoutManager"
        tools:listitem="@layout/item_task_detail" />

</LinearLayout>

CountryIndonesiaActivity.kt

class CountryIndonesiaActivity : BaseActivity() {
    private val viewModel by viewModel<CountryIndonesiaViewModel>()
    private lateinit var binding: ActivityCountryIndonesiaBinding
    private val viewAdapter by lazy { createAdapter(::onItemClicked) }

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        binding = ActivityCountryIndonesiaBinding.inflate(layoutInflater)
        setContentView(binding.root)
        setupActionBarWithBackButton(binding.toolbar)
        initView()

        viewModel.loadData()
    }

    private fun initView() {
        with(binding.recyclerView) {
            adapter = viewAdapter
            setHasFixedSize(true)
        }
    }

    override fun observeChange() {
        observe(viewModel.items, ::onDataLoaded)
        observe(viewModel.toastMessage, ::showSnackbarMessage)
    }

    private fun onDataLoaded(items: List<BaseViewItem>) {
        viewAdapter.submitList(items)
    }


    private fun onItemClicked(viewItem: BaseViewItem, view: View) {
        when (viewItem) {
            is DailyItem -> {

            }
            is TextItem -> {
                DailyGraphActivity.startActivity(this)
            }
        }
    }

    companion object {
        @JvmStatic
        fun startActivity(context: Context?) =
            context?.startActivity(Intent(context, CountryIndonesiaActivity::class.java))
    }
}

This question can be through kotlin-mvvm-covid19 project test.

Hi, I just tried out your library and I have to say: Awesome! I WILL use it in my projects from now on.

But it seems like adapterOf does not get imported automatically, so I had to search for the import in the sample app. Maybe you should add the note to the README that you need the import import me.ibrahimyilmaz.kiel.adapter.RecyclerViewAdapter.Companion.adapterOf like in the Download section.

Greetings!

In order to set hasStableId, we may pass lambda or interface to RecyclerViewAdapter to override getItemId.

When it is passed, RecyclerViewAdapter use it, When it is not passed, RecyclerViewAdapter default super.getItemId()

Aim is to make it composable also:

syntax would be:

val adapter =adapterOf<Type>{
         itemId{ t.getId() }
         ....
}

FEATURE REQUEST

Hi! Thank you for making Kiel! I've played with it for some time now and I want to use it in our project but this issue is we are trying to reduce build time by dropping jetifier.

We found out by dropping jetifier we can reduce a significant amount of build time. thank you!

Describe the solution you'd like

I've forked your project and dropped jetifier, test it and it works! I just disabled the app module because of some conflicts. Anyway it's working fine in my test project.

 implementation 'com.github.raquezha:kiel:1.2.1-beta'

Describe alternatives you've considered

I hope you consider this feature request

Additional context

1. Adam Bennet's Article about droping jetifier: https://adambennett.dev/2020/08/disabling-jetifier/
2. Can I Drop Jetifier Repo: https://github.com/plnice/can-i-drop-jetifier

Hi @ibrahimyilmaz, There is a common case that we will have a child list of items as a row of recyclerview just like Google Play did. Is there any solution for this case in Kiel?

Hi there, RecyclerView usually have to handle a large amount of data, I think it really need to add support for load more functions. What do you think?

Create alternative methods for register , where layoutResource is passed as a value, and then wrapped into a function type.

This

register(
    type = Text::class.java
    layoutResource = { R.layout.adapter_message_text_item }
    viewHolder = { ::TextMessageViewHolder }
    onViewHolderBound = { vh, _, it ->
        vh.messageText.text = it.text
        vh.sentAt.text = it.sentAt
    }
)

would become this: Kotlin

register(
    type = Text::class.java
    layoutResource = R.layout.adapter_message_text_item
    viewHolder = { ::TextMessageViewHolder }
    onViewHolderBound = { vh, _, it ->
        vh.messageText.text = it.text
        vh.sentAt.text = it.sentAt
    }
)

With:

fun register(layoutResourceProvider: () -> Int) {
    // use layoutResourceProvider
}

fun register(layoutResource: Int) = register(
    layoutResourceProvider = { layoutResource }
)

Proposed Changes/Issues Fixed

listAdapterOf DSL introduced. example syntax:

val adapter =listAdapterOf<Any> {
            itemDiffUtil { RecyclerViewItemCallback() }
            register { 
                type {  }
                viewHolder {  }
                layoutResource {  }
                onViewHolderBound { vh, i, it ->  }
                onViewHolderCreated<> { vh, i, it ->  }
                onViewHolderBoundWithPayload { vh, i, it, list ->  }<> { vh, i, it ->  }
            }
        }

Example:

General

• [x] Change/Fix added to CHANGELOG.md
• [x] Issue Link https://github.com/ibrahimyilmaz/kiel/issues/29
• [ ] Current Sample was changed/ new sample is introcuded

Testing

• [x] Unit-Tests implemented
• [x] Monkey-Test done
• [x] Does your submission pass ./gradlew check?

General

• [x] Change/Fix added to CHANGELOG.md
• [x] Issue Link https://github.com/ibrahimyilmaz/kiel/issues/72
• [ ] Current Sample was changed/ new sample is introcuded

Testing

• [ ] Unit-Tests implemented
• [x] Monkey-Test done
• [x] Does your submission pass ./gradlew check?

General

• [ ] Change/Fix added to CHANGELOG.md
• [ ] Issue Link
• [ ] Current Sample was changed/ new sample is introcuded

Testing

• [ ] Unit-Tests implemented
• [ ] Monkey-Test done
• [ ] Does your submission pass ./gradlew check?

Proposed Changes/Issues Fixed

Before publishing kiel to Maven Central, jcenter should be removed.

General

• [x] Change/Fix added to CHANGELOG.md
• [x] Issue Link https://github.com/ibrahimyilmaz/kiel/issues/72

Testing

• [x] Monkey-Test done
• [x] Does your submission pass ./gradlew check?

now we can register viewTypes but README has no way to determine which viewType is created at spefici position i.e how to make views has two types Head, Sub

• Head with odd positions
• Sub with even positions

https://github.com/ibrahimyilmaz/kiel/pull/40 added syntax to define Diff callback for whole adapter. But you still have no ability to define diff callback for register blocks separately.

There is example of how it may look like:

adapterOf<Animal> {
    register(
        layoutResource = R.layout.item_cat,
        viewHolder = ::CatHolder,
        diff = diff(
            areItemsTheSame = { cat1, cat2 -> cat1.name == cat2.name }
        )
    )

    register(
        layoutResource = R.layout.item_dog,
        viewHolder = ::DogHolder,
        diff = diff(
            areItemsTheSame = { dog1, dog2 -> dog1.bark == dog2.bark }
        )
    )
}

This builder under the hood should create single DiffUtil.Callback with multiple "delegates": one for Cat, one for Dog. Then, when DiffUtil.Callback methods are called, that Callback must pick appropriate "delegate" and call it