Bernard Siebens 413fea59f2 Remove RefereeLevel.ordering now inherits_from covers the same need ...

A separate manually-kept number for "which tier is higher" is
redundant now that the inheritance chain already expresses it, and
risked drifting out of sync with it. Levels list/sort by name only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ECGMEwrc2k4D8VQuwjstj9

2026-08-20 23:03:27 +02:00

..

migrations

Remove RefereeLevel.ordering now inherits_from covers the same need

2026-08-20 23:03:27 +02:00

__init__.py

feat(teams): add teams app with roster and staff assignments

2026-07-12 16:47:52 +02:00

admin.py

Remove RefereeLevel.ordering now inherits_from covers the same need

2026-08-20 23:03:27 +02:00

api.py

Checkpoint: management app redesign, onboarding/signup workflow, and events calendar backend

2026-08-19 23:34:43 +02:00

apps.py

feat(teams): add teams app with roster and staff assignments

2026-07-12 16:47:52 +02:00

models.py

Remove RefereeLevel.ordering now inherits_from covers the same need

2026-08-20 23:03:27 +02:00

services.py

Separate guardians from members: a parent is not automatically a member

2026-08-11 16:11:41 +02:00

tests.py

Let referee levels inherit from a lower level instead of relying on ordering alone

2026-08-20 22:42:18 +02:00

views.py

feat(teams): add teams app with roster and staff assignments

2026-07-12 16:47:52 +02:00