cubicweb #246927 generic subscription/notification interface [rejected]
at the moment, only some entities allow for notification of changes via hand-coded hooks. it would be interesting to research and implement a generic subscription/notification mechanism that most, if not all, objects would implement so that any object can be watched/monitored.
in the forge, projects can be monitored, but tickets cannot. in blog, blog can be monitored, but entries and comments cannot, etc.
Looks like there is a container/items pattern: project/tickets, project/versions, version/tickets, ticket/comments, blog/entries, entry/comments, project/tests, test/executions, etc. If the container is monitored, any change to itself or one of the items it contains will be notified.
|closed by||<not specified>|