First checks the project's root for a .podspec,
Then goes on to check the Local Pods folder,
if that can't be found raises an informative error.
Currently this breaks a couple of tests, as the behavior for sandbox#podspec_for_name(name) of returning nil apparently is being depended on. Submitting a pull request to begin the discussion.
Do you think this is the right approach?
The tests that are broken:
If you think this is the right approach, I'll look at how to fix these specs to not depend on a nil return value from that method.
Raise an informative error for missing podspec.
The issue appears to be in AbstractExternalSource#specification_from_sandbox and its interplay with sandbox#podspec_for_name(name).
We could raise in AbstractExternalSource or stop relying on the nil behavior. I, personally, don't have any preference, and I think it is mostly a (subjective) matter of which solution would be more idiomatic.
@alloy Any opinion on this?
I think moving it to the end of AbstractExternalSource#specification_from_sandbox is the better solution. It’s a problem which arises while trying to load the dependency.
Implemented by ae569fc.