aproxy | aproxy is a reverse proxy that includes authentication | Proxy library

Another possible solution could be based on an hand-knitted model and controller logic.

One would entirely separate the pure controller tasks, letting them only work directly with the DOM and with a modeled abstraction of the initially provided list items/values.

The model itself could be e.g. a Map based registry which implements the logic of always being in control of the correct list state.

Thus, in addition to the most obvious register/deregister methods, there will be sanitizing and check tasks that prevent e.g. double registering of (potentially) equal items/values. Such a registry model could also provide getters for special list representations of its registered items like e.g. providing the current array of just each item's text content or an array of each item's model.

As for the latter, such a model in addition to e.g. its id and text value would also feature its own view, e.g. an elm reference of the to be rendered/removed element node.

In order to keep each item specific DOM node and/or each item's model free of controller logic, the main controller task uses event delegation ^[1],[2] by listening to / handling the double-click event at the list's root-node exclusively.

The next provided example code demonstrates how the main controller task operates both the DOM and the item list abstraction ...