Skip to content

Strengthen app target detection beyond Info.plist paths #3

Closed

Description

@Zach677

Context

Current app target inference is intentionally conservative but still leans on simple filesystem signals such as */Resources/Info.plist. Real projects may use generated Info.plist files, target-specific build settings, extensions, or nonstandard folder layouts.

Scope

  • Parse enough .pbxproj structure to distinguish app targets from extensions, frameworks, test bundles, and resource bundles.
  • Prefer product type and target metadata over folder naming when available.
  • Keep behavior conservative when target ownership is ambiguous.

Acceptance

  • Repos with generated Info.plist do not become unsupported solely because the file is absent.
  • Extension-only signals do not cause the analyzer to treat an extension as the main app.
  • can_apply remains false when the main app target cannot be proven.

Activity

  1. linear-code commented on May 20, 2026

    @linear-code
  2. Zach677 commented on Jul 18, 2026

    @Zach677
    OwnerAuthor

    @Zach677 Fixed on main in d627e58. The analyzer now uses PBXNativeTarget product metadata, keeps extension-only projects non-applicable, and preserves AppKit repositories as read-only; CI passed for tooling, app builds, and tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions