← Back to issue list

Explicitly separate public and private APIs

View original Github issue

Metadata

Project
craft-application
Number
#386
Type
issue
State
open
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Feature request to explicitly separate public and private APIs in craft-application (e.g. launchpad, remote modules) to prevent every change from becoming a breaking change. No labels, no comments, no assignee; last activity 465 days ago.

Suggested action: needs triage

Reason: The issue has no labels, no comments, and no maintainer response, so it has not been triaged. It is a legitimate architectural concern (preventing breaking changes) that would require significant refactoring and backward-compatibility decisions, but there is no evidence it has been addressed or is no longer relevant.

Impact: 60 Quick Win: 15.0 Staleness: 70 Complexity: 75 Confidence: 75 Support Request: 0

Issue body

### What needs to get done Right now it's hard to know what's public and what's private. For example, the `launchpad` and `remote` modules are probably mostly private, but it's not explicit. ### Why it needs to get done We want to prevent every change from becoming a breaking change.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 60
Quick Win: 15.0
Staleness: 70
Complexity: 75
Confidence: 75
Support Request: 0
needs triage Feature request to explicitly separate public and private APIs in craft-application (e.g. launchpad, remote modules) to prevent every change from becoming a breaking change. No labels, no comments, no assignee; last activity 465 days ago.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 60
Confidence: 75
Support Request: 10
needs triage Issue proposes explicitly separating public and private APIs to prevent breaking changes. No maintainer response or labels. Inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 60
Confidence: 85
Support Request: 10
needs triage Proposes explicitly marking public vs private APIs to prevent breaking changes. Unlabelled, zero comments, and inactive for over two years, awaiting maintainer assessment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 78
Complexity: 50
Confidence: 90
Support Request: 5
needs triage Proposes explicitly separating public and private APIs to prevent unintended breaking changes. Open with zero comments and inactive for over a year. Requires triage and assignment to proceed.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.