Ali Asadi
0fe4a3ed79
The first attempt at this inferred the payout destination from PromotionTypeChoices (first_ad_view/capture/first_ad_create), a general promotion-category field that had never held real values. That coupled two independent facts together — a promotion's category and where its money goes aren't the same thing, and every new promotion type would need someone to remember to also classify it for wallet purposes. Revert PromotionTypeChoices to empty (left as pre-existing dead scaffolding, untouched) and add Recipient.wallet_destination instead — a real field that states the routing decision directly. Recipient.get_wallet_category_uuid() now branches on it: user_reward (default) resolves to WALLET_USER_BILLBOARD_VISIT_INCOME, advertising_transit resolves to WALLET_ADVERTISING_TRANSIT. An explicit Recipient.wallet_uuid still wins over either. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
19 lines
659 B
Python
19 lines
659 B
Python
from django.db import migrations, models
|
|
|
|
|
|
class Migration(migrations.Migration):
|
|
|
|
dependencies = [
|
|
('promotions', '0009_recipient_access_type_alloweduser'),
|
|
]
|
|
|
|
operations = [
|
|
migrations.AddField(
|
|
model_name='recipient',
|
|
name='wallet_destination',
|
|
field=models.CharField(choices=[('user_reward', 'user reward wallet'),
|
|
('advertising_transit', 'advertising transit wallet')],
|
|
db_index=True, default='user_reward', max_length=32,
|
|
verbose_name='wallet destination'),
|
|
),
|
|
]
|