Support Projects loaded from arbitrary URIs #21
Conversation
* In `EvaluatorOptions`, replace `ProjectDir` with `ProjectBaseURI` (API breaking) * `WithResourceReader` and `WithModuleReader` now append `:` to the scheme when appending to the allow-lists * Correct typo in `DeclaredProjectDepenedencies` (API breaking) * Add DEVELOPMENT.adoc with instructions on how to debug the `pkl server` subprocess * Miscellaneous doc comment clarifications
|
|
||
| = Pkl Go Development Guide | ||
|
|
||
| == Debugging the Pkl Server |
There was a problem hiding this comment.
@HT154 Does this work generally for debugging Pkl? I was just finding myself yesterday a bit annoyed at not being able to put breakpoints in Pkl sources.
There was a problem hiding this comment.
For debugging "regular" pkl eval invocations, you don't need to fuss with this, you can do it straight from intellij by finding the entrypoint (pkl-cli/src/main/kotlin/org/pkl/cli/Main.kt) and starting to run/debug from the main function. You can also modify the run configuration in that menu to pass CLI args, env vars, etc. as needed.
The approach documented here does work for general debugging as well, but it's required for debugging pkl server because the host process (eg. via pkl-go) currently must spawn the pkl process.
|
@bioball Is this good to merge now that apple/pkl#486 has merged? |
|
@HT154 yup--we're going to do a release soon so I'll get this in. |
Builds on apple/pkl#255 to allow fully in-memory evaluation of Pkl codebases using projects.
EvaluatorOptions, replaceProjectDirwithProjectBaseURI(API breaking)WithResourceReaderandWithModuleReadernow append:to the scheme when appending to the allow-listsDeclaredProjectDepenedencies(API breaking)pkl serversubprocess