notifications/apps/push_notifications/migrations
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
..
0001_initial.py send message api 2025-07-15 14:00:15 +03:30
0002_pushmessage_stats.py add celery 2025-07-17 12:03:18 +03:30
0003_bulkpushmessage_pushmessage_bulk.py bulk push 2025-07-19 15:41:36 +03:30
0004_pushmessage_click_url.py FEAT(notifications): add optional click_url for notification tap actions 2026-08-22 09:36:06 +03:30
0005_notificationlink_pushmessage_click_object_id_and_more.py FEAT(notifications): admin-managed code -> URL mapping for click actions 2026-08-22 14:35:55 +03:30
0006_rename_code_notificationlink_action_code_and_more.py 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