To ease contrib interoperability, we should define standard patterns for attaching displays to routes. Simply having modules fight over what's directly attached to the route isn't optimal, as it has the same "one slot master" problem that fighting over a page callback has today. We should see if we can come up with something better - though leaving it to a route alter fight will work, if need be.

Comments

andypost’s picture

andypost
he/him
Primary language Russian
commented

Suppose this easily solvable with prority of event listeners, so once one listener is not able to pass the selection criteria the request passed to original (core) listener otherwise "everywhere" listener returns responce