Add a way for applications to customize the `InitService`
Metadata
Current evaluation
Enhancement request for InitService to let applications customize project-name validation and emit template-specific messages. Name validation is already customizable via constructor args; unique per-template messages are not yet supported.
Suggested action: keep open
Reason: The issue is a labeled enhancement filed by a maintainer with an internal Jira ticket (CRAFT-3659), so it is triaged and valid. Code inspection shows name validation is already customizable (name_regex, invalid_name_message, default_name in InitService.__init__), but no mechanism exists for template-specific messages, so the request is only partially addressed and should remain open.
Impact:
40
Quick Win:
26.0
Staleness:
55
Complexity:
35
Confidence:
75
Support Request:
5
Issue body
### What needs to get done
The `InitService` should provide a clean way for applications to:
1. Validate the project name and other variables that will go into the template
2. Emit a message unique to each template
### Why it needs to get done
1. If the user provides an invalid name, the project will fail to build
2. Rockcraft provides different documentation links, depending on the template
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
26.0
Staleness:
55
Complexity:
35
Confidence:
75
Support Request:
5
|
keep open | Enhancement request for InitService to let applications customize project-name validation and emit template-specific messages. Name validation is already customizable via constructor args; unique per-template messages are not yet supported. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
40
Confidence:
75
Support Request:
5
|
needs triage | Enhancement to allow custom validation and messaging in InitService. Open for over a year with only an automated Jira sync comment and no maintainer triage or discussion. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | Enhancement request to allow application-level customization of the InitService for validation and templating. The issue has remained unassigned and inactive for over 10 months with only an automated Jira sync comment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
40
Confidence:
65
Support Request:
10
|
needs triage | Allows applications to customize the InitService for validating project names and emitting template-specific messages. Currently in backlog, last active 286 days ago, with an internal Jira ticket created. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.