-
Notifications
You must be signed in to change notification settings - Fork 143
//> using file directives should allow URLs and git repository paths #1328
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
Comments
Handling for remote sources is already in place for the command line, so this is a matter of porting this feature to the The standard entry point for inputs resolution is here: Where the interesting stuff starts here: scala-cli/modules/build/src/main/scala/scala/build/input/Inputs.scala Lines 319 to 333 in 4fb5c5b
Inputs (including remote ones) are validated here: scala-cli/modules/build/src/main/scala/scala/build/input/Inputs.scala Lines 225 to 232 in 4fb5c5b
All remote (virtual) inputs are then represented as instances of
The current implementation of the scala-cli/modules/directives/src/main/scala/scala/build/preprocessing/directives/Sources.scala Lines 12 to 29 in 4fb5c5b
Inputs from directives are then extracted here: scala-cli/modules/build/src/main/scala/scala/build/CrossSources.scala Lines 207 to 211 in 4fb5c5b
cc @tgodzik |
Oh, I didn't know "using file" is non-recursive. Then it seems much simpler |
It would be useful if the
//> using file
directives could accept URL and git repository paths in addition to local files. This would allow users to refer to their scala-cli module scripts from their executable scripts, no matter what paths the executable scripts were stored in:or
Deno has a similar feature for pulling in dependencies from URLs.
The text was updated successfully, but these errors were encountered: