notifications/apps/push_notifications
Ali Asadi 2dbe021fe5 REFACTOR(notifications): rename code/click_object_id to action_code/click_object_id_value
`code` was ambiguous next to Python's own use of "code"; `action_code` names
its actual role (a click-action lookup key). click_object_id_value pairs it
consistently with action_code. Renamed on both PushMessage and
NotificationLink via a data-preserving RenameField migration, threaded
through the serializer, admin, bulk-push path, and docs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-23 12:13:29 +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