Lars
4130a63dfe
All checks were successful
Deploy Development / deploy (push) Successful in 44s
Test Suite / pytest-backend (push) Successful in 42s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 13s
Test Suite / k6 /health Baseline (push) Successful in 35s
Test Suite / playwright-tests (push) Successful in 1m51s
- Updated the capability catalog to reflect a registry-first approach, requiring modules to register rights and quotas upon implementation. - Enhanced the backend to synchronize the rights registry with the database, ensuring only registered capabilities and features are displayed in the admin matrix. - Modified SQL queries in the admin rights router to filter capabilities and features based on module registration. - Updated documentation to clarify the new rights and features registry process, replacing the previous catalog-first method. - Incremented application version to 0.8.201 and updated database schema version to 20260606084 to reflect these changes.
25 lines
849 B
Python
25 lines
849 B
Python
from rights_registry import CapabilityRegistration, FeatureRegistration, register_capability, register_feature
|
|
|
|
_PLANNING_ROLES = ("club_admin", "trainer", "division_lead")
|
|
|
|
register_capability(
|
|
CapabilityRegistration(
|
|
id="planning.ai.suggest",
|
|
name="Planungs-KI Suggest",
|
|
domain="planning",
|
|
module="planning_exercise_suggest",
|
|
linked_feature_id="ai_calls",
|
|
default_club_grants=tuple((r, "planning.ai.suggest") for r in _PLANNING_ROLES),
|
|
)
|
|
)
|
|
register_capability(
|
|
CapabilityRegistration(
|
|
id="planning.ai.progression_path",
|
|
name="Planungs-KI Progressionspfad",
|
|
domain="planning",
|
|
module="planning_exercise_suggest",
|
|
linked_feature_id="ai_calls",
|
|
default_club_grants=tuple((r, "planning.ai.progression_path") for r in _PLANNING_ROLES),
|
|
)
|
|
)
|