Discuss: Interface for Moving an `item` from one `list` to another `list`?

[nelsonic]

Other list-based project management tools allow people to easily transfer items from one list to another,
How much do we want to "reinvent the wheel" on this functionality vs. just "copying" what people are already familiar with?

[LuchoTurtle]

I don't think we should "reinvent the wheel"/try to create a new UX to change lists. "Copying" what people are already familiar with will provide an easier onboarding experience and reduce initial frustration when first tinkering with the app.

I see our lists in a similar fashion to what happens with Overleaf when tagging documents.

We're just using it for categorization purposes, but with the added benefit of having specific UX for most used lists (shopping lists, exercise logs, for example).

However, thinking of how to implement this, relates to how we are saving our items in our database.

As mentioned in #418 (comment), we don't have any relation between the table items and lists. So changing an item from one list to another means having to change the seq field from a list and add it to another. Is there an efficient way of doing this? 💭

[nelsonic]

@LuchoTurtle by definition we always want the items to be in a sequence in the list.
So this is already the most efficient way of doing it. We don't need a relation. list.seq works.
If anything is unclear about this approach, please read the code:

mvp/lib/app/list.ex

Lines 149 to 154 in b8aee0e

	def add_item_to_list(item_cid, list_cid, person_id) do
	list = get_list_by_cid!(list_cid)
	prev_seq = get_list_seq(list)
	seq = [item_cid | prev_seq] |> Enum.join(",")
	update_list(list, %{seq: seq, person_id: person_id})
	end

It couldn't be easier to add an item to a list.
I tried several iterations of having a list_items table to join the data relationally and they all were more complex than this for maintaining the ordering (sequence) of the items in the list.