notifications/apps/push_notifications
Ali Asadi a84e2b3793 FEAT(notifications): pass action_code through in Gotify extras
get_gotify_extras() previously only ever surfaced the *resolved* click_url,
never the action_code that produced it -- so the frontend had no way to
know which action_code a notification carried, and got nothing at all for
a code that hasn't been configured in NotificationLink yet. Now
action_code rides along under client::notification.action_code whenever
it's set, independent of whether it resolved to a click_url. Verified live
against a running Gotify container, both resolved and unresolved.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-02 11:35:33 +03:30
..
management FEAT(notifications): management command to seed NotificationLink rows 2026-09-01 12:05:32 +03:30
migrations FIX(notifications): action_code accepts dots, PushMessage.stats actually updates 2026-09-01 15:55:17 +03:30
__init__.py send message api 2025-07-15 13:59:42 +03:30
admin.py REFACTOR(notifications): rename code/click_object_id to action_code/click_object_id_value 2026-08-23 12:13:29 +03:30
application_urls.py send message api 2025-07-15 13:59:42 +03:30
apps.py send message api 2025-07-15 13:59:42 +03:30
models.py FEAT(notifications): pass action_code through in Gotify extras 2026-09-02 11:35:33 +03:30
serializers.py REFACTOR(notifications): rename code/click_object_id to action_code/click_object_id_value 2026-08-23 12:13:29 +03:30
tasks.py FIX(notifications): action_code accepts dots, PushMessage.stats actually updates 2026-09-01 15:55:17 +03:30
tests.py send message api 2025-07-15 13:59:42 +03:30
user_urls.py send message api 2025-07-15 13:59:42 +03:30
views.py add celery 2025-07-17 12:15:32 +03:30