Skip to content
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

Suggestion: Ability to point to url of an API spec rather than a file #63

Open
nafg opened this issue May 21, 2020 · 3 comments
Open

Suggestion: Ability to point to url of an API spec rather than a file #63

nafg opened this issue May 21, 2020 · 3 comments

Comments

@nafg
Copy link

nafg commented May 21, 2020

No description provided.

@calvinbrown085
Copy link

Java IO file takes a https://docs.oracle.com/javase/7/docs/api/java/io/File.html#File(java.net.URI) URI, could we use that?

@blast-hardcheese
Copy link
Member

@calvinbrown085 The primary concern I had here was around the mechanics; just specifying a random URL, without caching, makes the project not able to be built offline.

Integrating with sbt/coursier/other resource caching would resolve this particular issue

@blast-hardcheese
Copy link
Member

Additionally, ideally (though this may be something that should come later), recognition of semver in the API would more accurately represent the changes in network semantics vs just arbitrarily alterations in service implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants