Skip to content

Expose planet production fees in the planet payload - #39

Open
Raukk wants to merge 1 commit into
PRUNplanner:mainfrom
Raukk:feat/planet-production-fees
Open

Expose planet production fees in the planet payload#39
Raukk wants to merge 1 commit into
PRUNplanner:mainfrom
Raukk:feat/planet-production-fees

Conversation

@Raukk

@Raukk Raukk commented Aug 13, 2026

Copy link
Copy Markdown

The FIO importer already syncs GamePlanetProductionFee per planet (planet_sync_production_fees), but GamePlanetSerializer doesn't expose it. This adds a nested production_fees field (category, workforce_level, fee_amount, fee_currency), the matching prefetch in queryset_gameplanet(), and an API test.

Related: A change (PR) on PRUNplanner/frontend reads this field to show production fees in the plan overview. It tolerates the field being absent, so merge order doesn't matter.

I'm really out of date with Python so I leaned on AI to make this change. Also, this is like my second opensource PR in a decade, please kindly let me know if I messed something up.

The FIO importer already syncs GamePlanetProductionFee per planet;
serialize it on GamePlanetSerializer so clients can read it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PFsCfBfPMjbxDYBoh65xYC
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants