MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj

Feature Request: Analyze in Xcode only runs against uppermost subset of targets

Open
#3,089 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Swift
Stars
626
Forks
124
PR merge metrics
No merged PRs in 30d

Description

Let me know if this is an inaccurate read of what is happening. From what I can see, when running Analyze against a target in Xcode (BwB, Bazel 7.3.1, rules_xcodeproj 2.7, rules_apple 3.8, rules_swift 2.1.1), the analyzer is only run against the source-list of the topmost library target in a top-level target. For example, the library of an ios_application, ios_unit_test, or ios_build_test. Sources in dependencies of that library target are not analyzed, and the analyzer doesn't appear to have much of an effect regardless.

Before I go through the process of sanitizing logs for y'all, does this sound familiar? Has the analyzer ever received attention in the ruleset? I would totally believe it if it had not yet.

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 reproducing Analyze in Xcode using the listed Bazel, rules_xcodeproj, rules_apple, and rules_swift versions, then inspect which target source lists are analyzed. Done means establishing whether dependency sources are omitted and defining a confirmed behavior or implementation scope for analyzing them.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
build-system, mobile-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.