Philip K.F. Hölzenspies

Avoiding resolution is fair enough. We were debating whether `download-package` _should_ exist. Its current UI does not know about `PklProject`, through. This is why `pkl download-package` does not (yet?) work...

> The error seems to suggest that there is no evaluation error here. This is because there isn't. Where you say `confUnderTest`, you just refer to the object; nothing's forcing...

> there doesn't seem to be any way to automatically format a Pkl file This isn't technically true; `pkl-intellij` has a formatter. Sadly, that's far too deeply integrated with the...

That's less simple than you might think. The generic informs the default / IDE type checking. It's a common pattern to define `Listing`s inline to produce something of a very...

You _might_ expect that, but does that mean you'd also expect that as soon as you're inside a function, you can't reference object properties at all anymore? How would you...

Totally what @HT154 said. Also, looking at your code, I'd suggest substituting lines 50-65 with ``` default { _port -> appProtocol = "HTTP" name = appProtocol.toLowerCase() protocol = "TCP" port...

The problem here is that the standard representation of a list of things in XML is to write out the elements consecutively. This is actually quite central in the XML...

This example case is somewhat fundamentally going to underperform. `kotlinx-serialization-properties` just parses this static data. Pkl brings a _lot_ more plumbing out of the box (and will take ~0.5-1s just...

@jackkleeman is entirely right and this is the starting point of `convert.pkl` scripts we sometimes write for specific schema (see [this example for k8s](https://github.com/apple/pkl-pantry/blob/main/packages/k8s.contrib/convert.pkl)). Converting JSON/YAML files to a Pkl...

It's not a general language construct; it's part of the standard library. We document individual modules (like `"pkl:json"` and `"pkl:yaml"`) there. As to CLI accessibility; it's not entirely clear what...