Skip to content

feat: add AppSettings model for centralized configuration - #148

Draft
geourjoa wants to merge 2 commits into
mainfrom
feat-1/app-settings-model
Draft

feat: add AppSettings model for centralized configuration#148
geourjoa wants to merge 2 commits into
mainfrom
feat-1/app-settings-model

Conversation

@geourjoa

@geourjoa geourjoa commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Add a table to centralize app settings. (Like enabled site feature and future improvement)

  • Adds a new AppSettings model (key/value/description/is_active/timestamps) to apps/common/models.py.
  • Kept as a separate model from SiteLabel (We can discuss to merge it but for me it's different concept)

Adds a per-key AppSettings model in apps.common, separate from SiteLabel,
for backend/operational config. value is a plain TextField (not JSONField)
since some entries are JSON-encoded strings that callers decode themselves.
Registered for audit tracking alongside SiteLabel since register_audited_models
works generically for any model.
AppSettings.__str__ returned self.key (a CharField descriptor typed as
Any) directly instead of wrapping it in str() like SiteLabel.__str__
already does, tripping mypy's no-any-return check in CI's lint job.

Also bumps cryptography>=49.0.0 -> >=50.0.0: CI's dependency-audit job
flags PYSEC-2026-3552 against 49.0.0, fixed in 50.0.0.
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.

1 participant