Linter to warn if the summary field is over 78 characters
Metadata
Current evaluation
Feature request to add a linter warning when charm summary exceeds 78 chars. Unimplemented; summary limit is currently 200 chars in project.py with a comment referencing this issue. No maintainer response beyond a bot Jira ticket sync. Last activity 381 days ago.
Suggested action: needs triage
Reason: The issue was filed by a maintainer (lengau) and synced to Jira (CRAFT-2599) but has no labels, no assignee, and no substantive maintainer discussion. The code comment in project.py (line 65) explicitly references this issue (#1598) and notes the 78-char limit is a future goal, confirming the feature is still unimplemented. However, with no activity in ~13 months and no triage labels, it needs a maintainer to decide whether to prioritize or defer it.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
26.25
Staleness:
72
Complexity:
25
Confidence:
78
Support Request:
0
|
needs triage | Feature request to add a linter warning when charm summary exceeds 78 chars. Unimplemented; summary limit is currently 200 chars in project.py with a comment referencing this issue. No maintainer response beyond a bot Jira ticket sync. Last activity 381 days ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add a linter warning when the metadata summary field exceeds 78 characters. Currently unlabelled and inactive for over a year, awaiting formal triage and prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add a linter warning for summary fields exceeding 78 characters. Currently untriaged, inactive for over 10 months, with only a bot-generated Jira ticket comment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
80
Support Request:
0
|
needs triage | Feature request to add a linter warning when the summary field exceeds 78 characters. Open since 2023 with no maintainer triage or implementation progress. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
65
Support Request:
10
|
needs triage | Add a linter warning for summary fields exceeding 78 characters. Charmcraft 3.0 limit broke charms, requiring a temporary warning until the limit is adjusted. Open, inactive for 304 days, unlabelled, and unassigned. Needs triage or assignment. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#1758
(confidence 85%)
Issue #1758 reported the 78-char max_length constraint causing validation errors; closed and linked to CRAFT-3146. This issue (#1598) is the follow-up feature request to add a linter warning instead of a hard limit.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1758 Max summary length is limited in metadata output | charmcraft | closed | Metadata summary validation incorrectly enforced a 78-character limit, causing charmcraft errors. The report was closed without a fix, merge, or code changes, indicating it was abandoned or handled externally. |