counterweight e7e3c97102 refactor(backend): standardize model-to-response conversion naming ... Issue #8: Inconsistent naming for model-to-response conversion functions. Changes: - Rename build_invite_response to _to_invite_response (invites.py) - Rename _map_counter_record to _to_counter_record_response (audit.py) - Rename _map_sum_record to _to_sum_record_response (audit.py) All conversion functions now follow the _to_X_response pattern, using underscore prefix for module-private functions.		2025-12-22 09:16:05 +01:00
..
__init__.py	first implementation	2025-12-20 22:18:14 +01:00
audit.py	refactor(backend): standardize model-to-response conversion naming	2025-12-22 09:16:05 +01:00
auth.py	Add ruff linter/formatter for Python	2025-12-21 21:54:26 +01:00
availability.py	refactor(backend): extract date range validation utilities	2025-12-22 00:02:41 +01:00
booking.py	refactor(backend): clean up router registration pattern	2025-12-22 09:10:26 +01:00
counter.py	Phase 2: Job enqueueing from counter	2025-12-21 22:44:31 +01:00
invites.py	refactor(backend): standardize model-to-response conversion naming	2025-12-22 09:16:05 +01:00
meta.py	refactor: derive Permission type from generated OpenAPI schema	2025-12-21 23:55:47 +01:00
profile.py	refactor(auth): unify authorization patterns with MANAGE_OWN_PROFILE permission	2025-12-21 23:50:06 +01:00
sum.py	Add ruff linter/formatter for Python	2025-12-21 21:54:26 +01:00