Skip to content

Move base-info endpoint into its own app - #53

Merged
FriggemannMichael merged 1 commit into
mainfrom
refactor/move-base-info-app
Jul 8, 2026
Merged

Move base-info endpoint into its own app#53
FriggemannMichael merged 1 commit into
mainfrom
refactor/move-base-info-app

Conversation

@FriggemannMichael

Copy link
Copy Markdown
Owner

Motivation

Mentor feedback (blocking): the base-info API view lives inside the core project package (core/api/), where it does not belong. core should only hold Django project configuration; the endpoint is a domain concern and belongs in its own app, consistent with the other *_app packages.

Changes

  • Add a dedicated base_info_app with apps.py, api/views.py (BaseInfoView), and api/urls.py.
  • Move the endpoint's tests into base_info_app/tests/.
  • Delete core/api/ entirely.
  • Register base_info_app in INSTALLED_APPS and point the api/ include at base_info_app.api.urls.
  • Extend test_app_architecture.py's EXPECTED_PROJECT_APPS with the new app.
  • Update the README project-structure section.

The URL name (base-info) and path (/api/base-info/) are unchanged, so no callers or contract tests change.

Verification

  • manage.py check: no issues
  • ruff: clean
  • pytest: 179 passed, coverage 98.27%

Relocate the base-info API out of the core project package into a
dedicated base_info_app, so core only holds project configuration.
The URL name stays 'base-info', so no callers change. Register the
new app, point the api include at it, move its tests, and extend
the architecture test's expected app list.
@FriggemannMichael
FriggemannMichael merged commit e697565 into main Jul 8, 2026
1 check passed
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