bazel-xcode / bazel-xcode/PodToBUILD

Cannot easily import pods by name

Open
#147 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Swift
Stars
330
Forks
68
PR merge metrics
No merged PRs in 30d

Description

Typically, the pod imports must be mangled with `PodToBUILD` to reflect the build target (referring to vendored pods here), like so:

**`Pods.WORKSPACE`**
```starlark
new_pod_repository(
name = "Hue",
url = "https://github.com/zenangst/Hue/archive/b9d920cee4ba795fefb828d130744eee1e3d2feb.zip",
inhibit_warnings = True,
)
```

_...later..._

**`BUILD.bzl`**
```
```

**`ViewController.swift`**
```swift
import Vendor_Hue_Hue_swift

// ...
```

It would be much cleaner if one could simply:
```swift
import Hue
```

as expected. This would also avoid tightly coupling source code to target paths, which might prevent easy refactoring down the road.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.