This release is a pre-release and may not be stable for production use.
forge-mvc-notifications
Notifications in-app opt-in pour Forge : créer des notifications destinées aux
utilisateurs (élève inscrit, note publiée, devoir à rendre) dans une table
notifications, les lire, les marquer comme lues.
Périmètre V1 : notifications in-app (des lignes en base, affichées dans l'IHM).
La livraison hors application (email, push) reste à la charge de l'application,
par exemple en combinant ce paquet avec forge-mvc-jobs et forge-mvc-mail.
Installation
pip install --pre forge-mvc-notifications
En développement : pip install -e ./packages/forge-mvc-notifications.
Mise en place de la table
forge notifications:init # copie la migration dans mvc/migrations/
forge migration:apply # crée la table notifications
Utilisation
from forge_mvc_notifications import notify, get_notifications, unread_count, mark_read
notify("eleve.42", "Votre note est publiée", type="info", data={"cours": "maths"})
print(unread_count("eleve.42")) # 1
for n in get_notifications("eleve.42", unread_only=True):
print(n.message, n.created_at)
mark_read(1)
L'API expose notify, get_notifications, unread_count, mark_read,
mark_all_read, plus Notification, NotificationError, TABLE_NAME,
MAX_LIMIT.
Afficher les notifications dans une page
from forge_mvc_notifications import register_notification_routes
register_notification_routes(router, recipient_of=lambda r: destinataire_de(r))
Quatre routes JSON : GET /api/notifications/unread-count,
GET /api/notifications (paginée par curseur), POST /api/notifications/{id}/read
et POST /api/notifications/read-all.
recipient_of est obligatoire. Le destinataire vient de la session, jamais de la
requête : accepter ?recipient=... donnerait à quiconque les notifications de
n'importe qui. Le marquage est borné au même destinataire.
Ces routes rendent du JSON et ne poussent rien ; le rafraîchissement s'écrit avec HTMX, que le squelette livre déjà.
Périmètre
- Stockage in-app uniquement (lignes en base).
- Routes JSON de lecture et de marquage, à câbler explicitement.
- Hors périmètre : livraison email/push (à combiner avec
forge-mvc-jobs+forge-mvc-mail), préférences de notification, poussée temps réel (SSE, WebSocket) et script de rafraîchissement.
Documentation complète : https://forgemvc.com/docs/forge/.
Metadata
Release files for forge-mvc-notifications 1.0.0rc9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| forge_mvc_notifications-1.0.0rc9.tar.gz | 30.1 kB | Without provenance | Details for forge_mvc_notifications-1.0.0rc9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| forge_mvc_notifications-1.0.0rc9-py3-none-any.whl | Python 3 | none | any | Details for forge_mvc_notifications-1.0.0rc9-py3-none-any.whl |
Total release size: 49.7 kB
Release files / forge_mvc_notifications-1.0.0rc9.tar.gz
| Download URL | forge_mvc_notifications-1.0.0rc9.tar.gz |
|---|---|
| Size | 30.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d3cc3867ca2072b4b7ef63a6083906457a6039b67729b4c2242d20aac85666d
|
|
BLAKE2b-256 checksum How to use checksums |
60267873e75454eac2470d6b9b5b101cbbf3503e04d1ec5e28e5ac0097e94b9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / forge_mvc_notifications-1.0.0rc9-py3-none-any.whl
| Download URL | forge_mvc_notifications-1.0.0rc9-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73638788b4851fb4b8b95127e785c04cca214beeb1d0961280bb868da905df7c
|
|
BLAKE2b-256 checksum How to use checksums |
6dcce36df623dd8c570f53f83d75bf25daf04255d7da6041b60ecddc6169dbc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for forge-mvc-notifications 1.0.0rc9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.