Make proposal limit customisable by conference

[marcoacierno]

Right now the "max 3 submissions per conference" is hardcoded in our API layer. We need to make this a new field in our conference settings

By default there should be no limit

[marcoacierno]

@claude work on this

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[claude]

Claude finished @marcoacierno's task in 3m 21s —— View job • claude/issue-4523-20260107-0109 • Create PR ➔

---

Implementation Complete ✅

I've successfully made the proposal submission limit customizable per conference. Here's what was done:

Changes Made

1. Added max_proposals field to Conference model (backend/conferences/models/conference.py)

   • Type: PositiveIntegerField (nullable, blank allowed)
   • Default: None (no limit)
   • Help text explains the field's purpose

2. Created database migration (backend/conferences/migrations/0056_conference_max_proposals.py)

   • Adds the new field to the conferences table

3. Updated API validation logic (backend/api/submissions/mutations.py:415-426)

   • Changed from hardcoded >= 3 check to using conference.max_proposals
   • Only enforces limit when max_proposals is not None
   • Dynamic error message shows the actual limit

4. Updated and added tests (backend/api/submissions/tests/test_send_submission.py)

   • Modified existing test to set max_proposals=3 on the conference
   • Added new test test_can_submit_unlimited_proposals_when_max_proposals_is_none to verify unlimited submissions work when field is None

Behavior

• Default: No limit (backward compatible - conferences without this field set can have unlimited proposals)
• With limit set: Enforces the configured limit (e.g., max_proposals=3 restricts to 3 proposals per user)
• Error message: Dynamically shows the actual limit to users

--- | Branch