[repository] set .eid on eschema when schema is loaded from the filesystem
enforcing the contract that a repository's schema should have .eid attribute of
entity schema set to the eid of the entity used to serialize them in the db.
Before this cset, this was not true during tests or for some c-c commands where
'quick_start' is set (eg db-restore, i18ncube...).
The change in server __init__ makes this assumption true during instance
creation: the serializing code was actually setting eid on schema object, but a
reference to a previously built schema was given instead of the one for the
latest created repository.
Closes #10450092
.. -*- coding: utf-8 -*-
Notifications management
========================
CubicWeb provides a machinery to ease notifications handling. To use it for a
notification:
* write a view inheriting from
:class:`~cubicweb.sobjects.notification.NotificationView`. The usual view api
is used to generated the email (plain text) content, and additional
:meth:`~cubicweb.sobjects.notification.NotificationView.subject` and
:meth:`~cubicweb.sobjects.notification.NotificationView.recipients` methods
are used to build the email's subject and
recipients. :class:`NotificationView` provides default implementation for both
methods.
* write a hook for event that should trigger this notification, select the view
(without rendering it), and give it to
:func:`cubicweb.hooks.notification.notify_on_commit` so that the notification
will be sent if the transaction succeed.
.. XXX explain recipient finder and provide example
API details
~~~~~~~~~~~
.. autoclass:: cubicweb.sobjects.notification.NotificationView
.. autofunction:: cubicweb.hooks.notification.notify_on_commit