• Marius Rackwitz's avatar
    Namespace the pod target product · 28463d4e
    Marius Rackwitz authored
    Pod target products are named after their specs. The namespacing cannot directly happen in the product name itself, because this must be equal to the module name and this will be used in source code, which should stay agnostic over the dependency manager. We need namespacing at all because multiple targets can exist for the same podspec and their products should not collide. This happens when mulitple user targets require the same pod, because they could require different sets of subspecs.
    28463d4e
Name
Last commit
Last update
bin Loading commit data...
examples Loading commit data...
lib Loading commit data...
spec Loading commit data...
.gitignore Loading commit data...
.gitmodules Loading commit data...
.kick Loading commit data...
.rubocop.yml Loading commit data...
.rubocop_cocoapods.yml Loading commit data...
.rubocop_todo.yml Loading commit data...
.travis.yml Loading commit data...
.yardopts Loading commit data...
CHANGELOG.md Loading commit data...
CONTRIBUTING.md Loading commit data...
Gemfile Loading commit data...
Gemfile.lock Loading commit data...
LICENSE Loading commit data...
README.md Loading commit data...
Rakefile Loading commit data...
cocoapods.gemspec Loading commit data...