← Back to issue list

Improve API naming and scoping

View original Github issue

Metadata

Project
craft-application
Number
#573
Type
issue
State
open
Author
sergiusens
Labels
—
Created
Updated
Closed
—

Current evaluation

Maintainer proposal to drop redundant Service suffix (PackageService -> services.Package) and tighten module scoping. Still unchanged at HEAD: no labels, comments, or decision on naming variant or back-compat.

Suggested action: needs triage

Reason: The issue has no labels, comments, or assignee, and HEAD still defines PackageService in craft_application/services/package.py and exports it from services/__init__.py, so this API redesign has not been assessed or implemented. The proposal is clear but leaves open which naming variant to adopt and how to handle backward compatibility.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 12 Complexity: 45 Confidence: 70 Actionability: 55

Issue body

### What needs to get done Do not be repetitive on names ``` craft_application.services.package.PackageService ``` Can be refactored to ``` craft_application.services.package.Package ``` or ``` craft_application.services._package.Package ``` and accessed as ``` craft_application.services.Package ``` or ``` from craft_application import services services.Package ``` ### Why it needs to get done - Easier use of the API - Less repetition - Better Scoping

Evaluation history

Date Model Scores Action Summary
~deepseek/deepseek-pro-latest
Impact: 40
Quick Win: 12
Complexity: 45
Confidence: 70
Actionability: 55
needs triage Maintainer proposal to drop redundant Service suffix (PackageService -> services.Package) and tighten module scoping. Still unchanged at HEAD: no labels, comments, or decision on naming variant or back-compat.
stealth/space-bunny-alpha
Impact: 30
Quick Win: 6
Complexity: 65
Confidence: 80
Actionability: 55
needs triage Maintainer proposal to drop redundant Service suffix (PackageService -> services.Package) and tighten module scoping. Still unchanged at HEAD: no labels, comments, or decision on which naming variant to adopt or how to handle back-compat.
qwen/qwen3.6-35b-a3b
Impact: 35
Quick Win: 14
Complexity: 45
Confidence: 65
Actionability: 75
needs triage Maintainer suggests renaming service classes (e.g., PackageService to Package) to reduce API repetition and improve scoping. No labels, comments, or assignee after 657 days.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 16
Staleness: 70
Complexity: 55
Confidence: 75
Support Request: 0
needs triage Refactor proposal to rename service classes (e.g. PackageService to Package) to reduce name repetition and improve API scoping. Unlabeled, no comments, no activity for ~15 months; the naming is still unchanged in the current codebase.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 40
Confidence: 75
Support Request: 10
needs triage Issue proposes refactoring API naming to reduce repetition (e.g., PackageService to Package). No maintainer response, no labels, inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 70
Confidence: 80
Support Request: 10
needs triage Suggests refactoring API class naming to remove redundant Service suffixes and improve module scoping. Unlabeled, authored by a maintainer, but has seen no discussion or engagement in over a year.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.