notifications/apps/push_notifications
Ali Asadi 3f739ad169 FEAT(notifications): management command to seed NotificationLink rows
Adds `seed_notification_links`, which upserts one NotificationLink row per
action_code documented in docs/frontend-notification-click-actions.md (12
billboard + 15 escrow codes), each active with a sample url_template
(https://app.gooyal.ir/ads/{object_id} / .../escrow/{object_id}). Lets
producer notifications resolve a click_url end to end today; the real
routes still need confirming with whoever owns the frontend, and can be
edited any time via the Django admin. Run with --force to overwrite rows
that already exist; existing rows are otherwise left untouched so manual
admin edits aren't clobbered by a rerun.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-01 12:05:32 +03:30
..
management FEAT(notifications): management command to seed NotificationLink rows 2026-09-01 12:05:32 +03:30
migrations REFACTOR(notifications): rename code/click_object_id to action_code/click_object_id_value 2026-08-23 12:13:29 +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 REFACTOR(notifications): rename code/click_object_id to action_code/click_object_id_value 2026-08-23 12:13:29 +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 FEAT(notifications): add optional click_url for notification tap actions 2026-08-22 09:36:06 +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