Bazel target product name places "-Bazel" after product extension (.app, .appex, ...)

Open
#92 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
swift
Domain
build-system

Research direction

Start by locating the code that generates BuildableName values for Bazel schemes in the generated Xcode project. Compare the current placement of the -Bazel suffix with Xcode's corrected output, especially for .app and .appex products. Done means generated buildable names place the suffix before the product extension rather than after it.

Written by the indexing model from the issue text.

Description

Here is an example diff of what happens today.

       <BuildableReference
             BuildableIdentifier = "primary"
-            BlueprintIdentifier = "NT_217978137037"
-            BuildableName = "share-extension-Bazel.appex"
+            BlueprintIdentifier = ""
+            BuildableName = "share-extension.appex-Bazel"
             BlueprintName = "share-extension-Bazel"
             ReferencedContainer = "container:UrlGet.xcodeproj">
          </BuildableReference>

If you open the project in Xcode it'll fix this for you but we should be generating the buildable name for Bazel schemes.

Dominant language
Swift
Stars
314
Forks
45
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from bazel-xcode/xchammer

All issues in bazel-xcode/xchammer

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.