Module name typo: `model_managment_app.py` should be `model_management_app.py`

Open Beginner friendly
#3,698 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
backend, documentation, testing

Research direction

Start with backend/apps/model_managment_app.py, test/backend/app/test_model_managment_app.py, backend/apps/config_app.py:16, and the four documentation references listed in the issue. Rename the module and test, update every reference, then run the renamed backend app test and verify no managment references remain.

Written by the indexing model from the issue text.

Description

Currently:

  • backend/apps/model_managment_app.py
  • test/backend/app/test_model_managment_app.py
  • Referenced from backend/apps/config_app.py:16: 
    from apps.model_managment_app import router as model_manager_router
  • And mentioned in doc/docs/{en,zh}/backend/overview.md:25, doc/docs/{en,zh}/getting-started/software-architecture.md:35, doc/docs/{en,zh}/testing/backend.md:22-23.

managment is a misspelling of management. Every other module in backend/apps/ and every service/database peer use the correctly-spelled form, e.g.:

backend/apps/user_management_app.py
backend/services/model_management_service.py
backend/services/user_management_service.py
test/backend/services/test_model_management_service.py

So this file is the lone outlier — even its own service-layer counterpart got the spelling right. It's a small thing, but module-name typos compound: every git grep, every import, every doc reference now has to remember which subsystem mis-spelled it.

Fix
git mv backend/apps/model_managment_app.py backend/apps/model_management_app.py
git mv test/backend/app/test_model_managment_app.py test/backend/app/test_model_management_app.py

…then fix the import in backend/apps/config_app.py:16 and the four doc references.

Category: F (docs/code mismatch — and code/code mismatch with the rest of the module taxonomy). Severity: Low (cosmetic), but easy to ship the fix.

Dominant language
Python
Stars
5.9k
Forks
731
Avg merge
16h 45m
Merged PRs (30d)
181

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ModelEngine-Group/nexent

All issues in ModelEngine-Group/nexent

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.