regal | A/B Testing or publish smart grouping engine

Make it as simple as possible and do not store the information from different loops in these bunch of lists, try to store them in one dict:

If two words are anagrams, they have the same numbers of same letters:

The issue is in these 3 lines.

rename works for me, perhaps you have a function conflict with another package. Try using dplyr::rename.

To change the columns based on range of values you may use case_when or cut.

If I understand the documentation correctly, backgroundColor in extend section is only used for adding states (like active which is in example).

If you would like to extend it via the default palette you can place it to the theme (without extend) and spread the default values via JavaScript:

You have too much code too see where the problem is happening. Is this the filter you are looking for?

You can make use of String#includes() and String#charAt() to check each character in the userGuess against the pickedWord.

The snippet below uses the results to wrap each character in a span of the appropriate color. You can refactor the HTML generated as needed.

How is it possible to ...

You have a ViewModel and it exposes two observable liveData with the List that your RecyclerViews need (two adapters, two lists).

The logic to decide that List A, Item 1 was tapped, and therefore List B, Item N has to change its background is absolutely outside of the scope of the Recycler View, Adapter, Activity, and possibly even ViewModel.

Ultimately, when a data mutation occurs (you tapped Item 1), you receive this event, act upon it (aka: send it to the Viewmodel -> Repository -> transform the data -> publish new lists(s) with the mutated data.

Eventually, your ViewModel will receive the new data from the repository, and will update the LiveData(s) that your activity is observing, and this will result in the adapters being submitted new data, that your DiffUtils will pick up, causing the Adapter to re-bind the modified views.

Based on the question/answer you linked, and your comment, I think this deserves a further comment.

1. The person says: "it's not a good idea to handle click on the adapter, nor to use an interface", then proceeds to "handle" the click, and uses an anonymous function (so it could have been an interface for the purposes of testing, but it instead made it a "higher order function".

2. This is exactly the same principle I was describing, only an interface is easier to understand.

Think about the responsibilities like this:

ViewHolder: It knows nothing about the data, recycler view, adapter, etc. But it has direct access to each "row/column" of your List. It owns the views, and it can manipulate them based on the data it's supplied and told to "hold" alongside the needed views. It doesn't create the views (it's told to) but it has them. All this can do in regards of clicking, is to make either expose a view (so a click listener can be set by someone externally) or simply delegate it.

Adapter: It knows nothing about the views other than their type (if used) and how to create viewHolders and "bind" them. So it sits in between, but it does have access to the data source provided to it (the list you supply) and it does have access to each "view holder" that it created; it knows more or less what's on screen, and can map a position to the data.

RecyclerView/Fragment/ViewModel: these have no idea what happens inside an adapter (nor they should), but they are primarily interested in when a click (or event) happened so they can presumably do something about it.

Based on all this, let's look at this person's solution (vs. what I was suggesting):

1. The Adapter's constructor is modified to receive a function:

(private val onSelect: (YourDataType?) -> Unit)

I normally define an interface:

I think the easiest way to achieve this is to define a tidy_custom.polr method as described here in the documentation.. For instance, you could do: