-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linting source of a spec is broken for certain URLs #82
Comments
Failing tests: diff --git a/spec/specification/linter_spec.rb b/spec/specification/linter_spec.rb
index b1b2ad6..68cee27 100644
--- a/spec/specification/linter_spec.rb
+++ b/spec/specification/linter_spec.rb
@@ -263,7 +263,7 @@ module Pod
@spec.stubs(:source).returns({ :git => 'http://repo.git', :tag => '1.0' })
message_should_include('git', 'version', 'tag')
end
-
+
it "checks that the version is included in the git tag when the version is a Version" do
@spec.stubs(:version).returns(Version.new '1.0.1')
@spec.stubs(:source).returns({ :git => 'http://repo.git', :tag => (Version.new '1.0') })
@@ -286,6 +286,18 @@ module Pod
@linter.results.should.be.empty
end
+ it "does not warn for local repositories with spaces" do
+ @spec.stubs(:source).returns({ :git => '/Users/kylef/Projects X', :tag => '1.0' })
+ @linter.lint
+ @linter.results.should.be.empty
+ end
+
+ it "does not warn for SSH repositories with" do
+ @spec.stubs(:source).returns({ :git => '[email protected]:kylef/test.git', :tag => '1.0' })
+ @linter.lint
+ @linter.results.should.be.empty
+ end
+
it "performs checks for Gist Github repositories" do
@spec.stubs(:source).returns({ :git => "git://gist.github.com/2823399.git", :tag => "1.0" })
message_should_include('Github', 'https') |
I can fix those, but wondering what e.g. |
Started a PR for this. Like I said, I am not sure what the behavior for SSH URLs on GitHub should be, but they should probably be valid as well. |
For context the reason why |
👍 For private pods we use SSH links not https. |
Closed by #84 |
... and released as CocoaPods 0.31.1 |
Looks like #77 was a bad idea.
The text was updated successfully, but these errors were encountered: