Philip K.F. Hölzenspies
Philip K.F. Hölzenspies
Yeah, I see the value of consistency in the naming, but it is indeed a breaking change. Thoughts, @bioball / @stackoverflow?
I thought it wasn't extended to Kotlin toolchains yet in Gradle 7 (and we're still pending the bump to >=8.6)
I forget about the Kotlin stdlib intricacies for `shadowJar`. @stackoverflow / @bioball, thoughts?
A `nix` output format is certainly a reasonable way in, although that could just be a renderer *in* Pkl (see the [TOML renderer](https://github.com/apple/pkl-pantry/blob/main/packages/pkl.toml/toml.pkl)). That said, the `nix` format has a...
Digging into that flakey test.
> @holzensp All tests that use PackageServer are flaky. Higher Gradle versions just seem better at exposing the flakiness. The proper fix is to bind PackageServer to a dynamic port....
Much appreciated @translatenix. @KushalP is also working on a PR to avoid port binding conflicts when tests are run in parallel. The tests really aren't rigid enough. Your #157 will...
Terribly sorry; I was entirely off-the-grid for a couple of weeks. Circling back to this tomorrow.
You could define (using `import "pkl:reflect"`): ``` function expectedKeys(clazz: reflect.Class?): Set = if (clazz == null) Set() else clazz.properties.keys + expectedKeys(clazz.superclass) function hasAdditionalFields(object: Dynamic, clazz: Class): Boolean = let (props...
Layers of “built-in.” For sure there is a place for this in `pkl-pantry`. I was thinking about being built-in in the language, and the problem there is that there are...