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.