How to remove defaults from configuration?

[kaihendry]

The goal in my workplace is to reduce the complexity of configuration by inferring "defaults".

The idea is that if the configuration has a default expressed in the schema, why not omit it or refactor the configuration?

For example:

extends "schema.pkl"

name = "foo"
auto_resume = false

open module com.example.Blueprint

name: String
auto_resume: Boolean = false

Since auto_resume is false by default, how do I warn or remove the auto_resume = false line from the config.pkl?

[HT154]

There's no automatic way to do this in Pkl today, unfortunately. It's a problem I've run up against in the past myself.

It's probably worth filing an issue describing how you'd like to see this functionality/tooling work!

[madrob]

I think this would be part of apple/pkl-evolution#9

[HT154]

Hmm, I think this is more of a static analysis and linting problem than a runtime feature for removing properties/entries/elements in Dynamic/Mapping/Listing. I think @kaihendry's desire here is to warn or automatically eliminate cases where an extend/amend of a type or value assigns the same literal value as its parent with the goal of removing repetition of value where it's not needed.