Philip K.F. Hölzenspies
Philip K.F. Hölzenspies
It's a totally legit ask. For other output formats, especially "simpler" ones, we recommend implementing them in Pkl itself. We did this with the TOML renderer, for example: https://github.com/apple/pkl-pantry/tree/main/packages/pkl.toml Since...
Fixed by PR #73
The stack overflow is expected, although arguably it's missing a stack frame (cc @stackoverflow and not just for the ironically appropriate username). In Pkl, `a = a` is the simplest...
Can you share some versions of things? At least the version of your `nvim` and the `tree sitter` package installed for that?
A part of the problem is that _matching_ common practice would require defining properties for all providers on one level, because HCL just merges the namespaces for everything. That is,...
This was actually covered by #44. Thanks for the help, though.
Shooting from the hip, but I'd imagine _all_ of these tests have become flakey since the Gradle bump. We should kick this off again after that's reverted.
This is an instance of https://github.com/apple/pkl/issues/405 `new Foo {}` only derives what default value to amend from `Foo`; it does not _check_ the amended result. This is one of the...
Instead of adding a `--download` argument, we're considering just always downloading (unless `--no-cache` is specified).
We did discuss it. When using `pkl project resolve --no-cache`, it would not download things. That does feel less that optimally discoverable, to be sure, but our thinking so far...