-
-
Notifications
You must be signed in to change notification settings - Fork 105
Dependency cli parsing #673
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
base: master
Are you sure you want to change the base?
Changes from 9 commits
1e95757
aae1479
eafca30
040cbdd
53353dc
91c3656
47ec209
ac81d3c
d03ae53
05f3d97
05483f2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,75 @@ | ||
require "./spec_helper" | ||
require "../../src/dependency_definition" | ||
|
||
private def expect_parses(value, resolver_key : String, source : String, requirement : Shards::Requirement) | ||
Shards::DependencyDefinition.parts_from_cli(value).should eq(Shards::DependencyDefinition::Parts.new(resolver_key: resolver_key, source: source, requirement: requirement)) | ||
end | ||
|
||
module Shards | ||
describe DependencyDefinition do | ||
it ".parts_from_cli" do | ||
# GitHub short syntax | ||
expect_parses("github:foo/bar", "github", "foo/bar", Any) | ||
expect_parses("github:Foo/[email protected]", "github", "Foo/Bar", VersionReq.new("~> 1.2.3")) | ||
|
||
# GitHub urls | ||
expect_parses("https://github.com/foo/bar", "github", "foo/bar", Any) | ||
|
||
# GitHub urls from clone popup | ||
expect_parses("https://github.com/foo/bar.git", "github", "foo/bar", Any) | ||
expect_parses("[email protected]:foo/bar.git", "git", "[email protected]:foo/bar.git", Any) | ||
|
||
# GitLab short syntax | ||
expect_parses("gitlab:foo/bar", "gitlab", "foo/bar", Any) | ||
|
||
# GitLab urls | ||
expect_parses("https://gitlab.com/foo/bar", "gitlab", "foo/bar", Any) | ||
|
||
# GitLab urls from clone popup | ||
expect_parses("https://gitlab.com/foo/bar.git", "gitlab", "foo/bar", Any) | ||
expect_parses("[email protected]:foo/bar.git", "git", "[email protected]:foo/bar.git", requirement: Any) | ||
|
||
# Bitbucket short syntax | ||
expect_parses("bitbucket:foo/bar", "bitbucket", "foo/bar", Any) | ||
|
||
# bitbucket urls | ||
expect_parses("https://bitbucket.com/foo/bar", "bitbucket", "foo/bar", Any) | ||
|
||
# unknown https urls | ||
expect_raises Shards::Error, "Cannot determine resolver for HTTPS URI" do | ||
Shards::DependencyDefinition.parts_from_cli("https://example.com/foo/bar") | ||
end | ||
|
||
# Git convenient syntax since resolver matches scheme | ||
expect_parses("git://git.example.org/crystal-library.git", "git", "git://git.example.org/crystal-library.git", Any) | ||
expect_parses("[email protected]:foo/bar.git", "git", "[email protected]:foo/bar.git", Any) | ||
|
||
# Local paths | ||
local_absolute = "/an/absolute/path" | ||
local_relative = "an/relative/path" | ||
|
||
# Path short syntax | ||
expect_parses("../#{local_relative}", "path", "../#{local_relative}", Any) | ||
{% if flag?(:windows) %} | ||
expect_parses(".\\relative\\windows", "path", "./relative/windows", Any) | ||
expect_parses("..\\relative\\windows", "path", "../relative/windows", Any) | ||
{% else %} | ||
expect_parses("./#{local_relative}", "path", "./#{local_relative}", Any) | ||
{% end %} | ||
# Path file schema | ||
expect_raises Shards::Error, "Invalid file URI" do | ||
Shards::DependencyDefinition.parts_from_cli("file://#{local_relative}") | ||
end | ||
expect_parses("file:#{local_relative}", "path", local_relative, Any) | ||
expect_parses("file:#{local_absolute}", "path", local_absolute, Any) | ||
expect_parses("file://#{local_absolute}", "path", local_absolute, Any) | ||
# Path resolver syntax | ||
expect_parses("path:#{local_absolute}", "path", local_absolute, Any) | ||
expect_parses("path:#{local_relative}", "path", local_relative, Any) | ||
# Other resolvers short | ||
expect_parses("git:git://git.example.org/crystal-library.git", "git", "git://git.example.org/crystal-library.git", Any) | ||
expect_parses("git+https://example.org/foo/bar", "git", "https://example.org/foo/bar", Any) | ||
expect_parses("git:https://example.org/foo/bar", "git", "https://example.org/foo/bar", Any) | ||
end | ||
end | ||
end |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,96 @@ | ||
require "./dependency" | ||
|
||
module Shards | ||
class DependencyDefinition | ||
record Parts, resolver_key : String, source : String, requirement : Requirement = Any | ||
|
||
property dependency : Dependency | ||
# resolver's key and source are normalized. We preserve the key and source to be used | ||
# in the shard.yml file in these field. This is used to generate the shard.yml file | ||
# in a more human-readable way. | ||
property resolver_key : String | ||
property source : String | ||
|
||
def initialize(@dependency : Dependency, @resolver_key : String, @source : String) | ||
end | ||
|
||
# Used to generate the shard.yml file. | ||
def to_yaml(yaml : YAML::Builder) | ||
yaml.scalar dependency.name | ||
yaml.mapping do | ||
yaml.scalar resolver_key | ||
yaml.scalar source | ||
dependency.requirement.to_yaml(yaml) | ||
end | ||
end | ||
|
||
# Parse a dependency from a CLI argument | ||
def self.from_cli(value : String) : DependencyDefinition | ||
parts = parts_from_cli(value) | ||
|
||
# We need to check the actual shard name to create a dependency. | ||
# This requires getting the actual spec file from some matching version. | ||
resolver = Resolver.find_resolver(parts.resolver_key, "unknown", parts.source) | ||
version = resolver.versions_for(parts.requirement).first || raise Shards::Error.new("No versions found for dependency: #{value}") | ||
spec = resolver.spec(version) | ||
name = spec.name || raise Shards::Error.new("No name found for dependency: #{value}") | ||
|
||
DependencyDefinition.new(Dependency.new(name, resolver, parts.requirement), parts.resolver_key, parts.source) | ||
end | ||
|
||
# :nodoc: | ||
# | ||
# Parse the dependency from a CLI argument | ||
# and return the parts needed to create the proper dependency. | ||
# | ||
# Split to allow better unit testing. | ||
def self.parts_from_cli(value : String) : Parts | ||
uri = URI.parse(value) | ||
|
||
case scheme = uri.scheme | ||
when Nil | ||
case value | ||
when .starts_with?("./"), .starts_with?("../") | ||
Parts.new("path", Path[value].to_posix.to_s) | ||
when .starts_with?(".\\"), .starts_with?("..\\") | ||
{% if flag?(:windows) %} | ||
Parts.new("path", Path[value].to_posix.to_s) | ||
{% else %} | ||
raise Shards::Error.new("Invalid dependency format: #{value}") | ||
{% end %} | ||
when .starts_with?("git@") | ||
Parts.new("git", value) | ||
else | ||
raise Shards::Error.new("Invalid dependency format: #{value}") | ||
end | ||
when "file" | ||
raise Shards::Error.new("Invalid file URI: #{uri}") if !uri.host.in?(nil, "", "localhost") || uri.port || uri.user | ||
Parts.new("path", uri.path) | ||
when "https" | ||
if resolver_key = GitResolver::KNOWN_PROVIDERS[uri.host]? | ||
Parts.new(resolver_key, uri.path[1..-1].rchop(".git")) # drop first "/"" | ||
else | ||
raise Shards::Error.new("Cannot determine resolver for HTTPS URI: #{value}") | ||
end | ||
else | ||
scheme, _, subscheme = scheme.partition('+') | ||
subscheme = subscheme.presence | ||
if Resolver.find_class(scheme) | ||
if uri.host.nil? || subscheme | ||
uri.scheme = subscheme | ||
end | ||
source = uri.to_s | ||
# narrow down requirement | ||
requirement = Any | ||
if source.includes?("@") | ||
source, version = source.split("@") | ||
requirement = VersionReq.new("~> #{version}") | ||
end | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. issue: Splitting on Even then, there's a chance for misinterpretation because Nix flake uses query parameters to encode version information (e.g. I think this is not entirely elegant because query parameters have a different purpose. They're supposed to be resolved by the remote party. The URI fragment is more elegant for this. It represents resource-internal information resolved by the local party. So URLs would look like this: We can further enhance this by adding support for parameters to the fragment, thus being able to resolve fragments like There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wouldn't that # force the need of quoting in the shell? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No. You can use URLs with fragments perfectly fine in shell commands. The shell considers $ echo foo#bar
foo#bar
$ echo foo #bar
foo There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Using fragments for version numbers with the same semantics currently have @ seems good to me. Tag and branch (and revision/commit) can come later imo. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It may work, but other package managers (cargo, bundler, ...) use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like more
It seems that Any final calls? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm wondering if we need to fix this now. We could leave version restrictions out of this first step and continue the discussion on that separately, while moving forward with producing an MVP. Having support for restrictions is useful, but not essential for a working prototype. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we do. I rather support github:owner/repo with version rather than all the other combinations we've been discussing. It seems that it will be more used IMO. python pip uses I would stick with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not happy about jumping to a syntax for one use case without proper consideration of other related applications. Even if it's for the most common use case. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The fact shards encourage semver, calver seems good enough for me to make @ or whatever syntax that mentions just a version to mean ~>. I would leave out for now any other version operator. I don't mean to jump. I mean to discuss and decide. I don't want to not support ~> version restriction out in this first cut. |
||
|
||
return Parts.new(scheme, source, requirement) | ||
end | ||
raise Shards::Error.new("Invalid dependency format: #{value}") | ||
end | ||
end | ||
end | ||
end |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought: I'm wondering about why this gets normalized to
github
resolver instead of"git", "https://github.com/foo/bar"
.Both options are valid. So we only need to decide which one we want to pick.
I suppose the reason for
github
is that it's more concise? That's nice but not strictly necessary.git
would be closer to the original input.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me closer to the intent is to have
github: foo/bar
, because I'm assuming the user is copy-pasting the url in the browser. We do preserve the format with trailing .git as those are copied from the clone popup.At some point maybe it's worth configuring shards to map all github source to be resolved in some specific way, but is a separate story.