realm/SwiftLint

`generic_type_name` triggers incorrectly for integer generic parameters

Open

#6,213 建立於 2025年8月30日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Swift (19,570 star) (2,295 fork)batch import
enhancementgood first issue

描述

Bug Description

SE-0452 introduced integer generic parameters, which are placed alongside other generic parameters, but, in contrast to "normal" (type) generic parameters, are spelled like variables, ie starting with a lowercase identifier. SwiftLint current;y doesn

// This triggers a violation:
struct Foo<let count: Int> {}

Mention the command or other SwiftLint integration method that caused the issue. Include stack traces or command output.

$ swiftlint

Environment

  • SwiftLint version: 0.59.1 (Homebrew)
  • Xcode version: Xcode 26.0 (17A5305f)
  • Configuration file: default configurations

貢獻者指南

技術棧
swift
領域
toolingdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Swift genericsSwiftLint rule structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Examine the `GenericTypeNameRule` implementation in SwiftLint's source code (likely under `Source/SwiftLintFramework/Rules/`). Understand how the rule currently identifies generic type names and why integer generic parameters (introduced in SE 0452) are incorrectly triggering. Look at the existing test cases for that rule and add a new test case for `struct Foo<let count: Int> {}`. The fix likely involves updating the rule's logic to exclude integer generic parameters from the name check.