realm / realm/SwiftLint

Rule Request: [duplicate_target_in_package]

Open
#4,805 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

rule-request
Dominant language
Swift
Stars
19.7k
Forks
2.3k
Avg merge
1d 1h
Merged PRs (30d)
11

Description

New Issue Checklist
New rule request

This rule would warn about duplicate targets in a Package.swift file.

Violation:

let package = Package(
    name: "MyPackage",
    platforms: [.iOS(.v14)],
    products: [
        .library(
            name: "MyPackage",
            targets: [
                "BigDependency",
                "SmallDependency",
                "OtherDependency",
                "BigDependency"
            ]),
    ],

Non-violation

let package = Package(
    name: "MyPackage",
    platforms: [.iOS(.v14)],
    products: [
        .library(
            name: "MyPackage",
            targets: [
                "BigDependency",
                "SmallDependency",
                "OtherDependency"
            ]),
    ],

I've seen this problem occur usually when there are two people working on the same swift package. One of them adds a dependency. And the other adds another, and then the branches are merged. It isn't flagged as a problem by the compiler, but can cause issues.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing SwiftLint’s existing rule entry points and test conventions, then use the Package.swift violation and non-violation examples as the behavioral cases. Done means duplicate target names in a Package.swift file produce a warning while unique target names do not.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.