cubicweb-container #3497714 recommend to subclass adapter and hook classes instead of overriding their selector [resolved]

The documentation and tests often recommend to set the selector of container classes. e.g. from test2/data/entities.py:

from cubes.container.entities import Container
[...]
def registration_callback(vreg):
    Container.__select__ = is_instance('Project', *(proj_etypes | fold_etypes))

It seems to me that this is rather fragile (e.g. if several cubes in the same application try to configure container this way). The doc and tests should recommend to subclass these classes in client code. Then, the yet_unset predicates (that currently emits warnings if one does so) could be dropped.

prioritynormal
typeenhancement
done in2.4.0
load0.200
load left0.000
closed by#a789ce5a24fe Drop the yet_unset selector and make classes previously using it abstract, #52852feface1 Drop any usage of the yet_unset pseudo-selector and make the adapters using it __abstract__.
patchDrop the yet_unset selector and make classes previously using it abstract [applied]Drop any usage of the yet_unset pseudo-selector and make the adapters using it __abstract__. [applied]