Thanks! That works great. I had no ideamodule was a keyword.

As a follow up, is there a way to do something similar for amended objects?

Can you elaborate on that? Do you have an example?

I realized that the amending syntax for objects forces you to give them an identifier in scope, so this isn't an issue.

i.e in

tortoise = (dodo) {name ="Galápagos tortoise"taxonomy {`class` ="Reptilia"   }}

dodo is accesssible inside the definition oftortoise

Gotcha.

Also, there issuper, which is useful in cases where you have an amends declaration. For example:

tortoise {name ="\(super.name) tortoise"taxonomy {`class` ="Reptilia"   }}

Note thattortoise { ... } is practically the same astortoise = (super.tortoise) { ... }.

I found this and I have the feeling my case / question is similar but I don't get it to work.
My template:

something .. somethinglocalbaseHeaderComment ="# Do not modify!\n# This file was generated from a template using https://github.com/StefMa/pkl-gha"headerComment:String?=nulllocal finalHeaderComment:String=if (headerComment!=null)"\(headerComment)\n\n"+ baseHeaderCommentelse baseHeaderCommentoutput {text ="\(finalHeaderComment)\n\n\(super.text)"renderer =newYamlRenderer{converters {      ["headerComment"]= (headerComment:String?)->null    }  }}

My consumercan (don`t have to) override it like this:

amends"../GitHubAction.pkl"headerComment ="""  # SPDX-FileCopyrightText: Copyright line here  #  # SPDX-License-Identifier: License here  """

However, I don't like that I have theheaderComment as a "templating value".
Actually it isn't something for the (in this case) GitHub Action yml directly.
I would be more happy if I could to likemodule.headerComment = "" orsuper.headerComment = "".
Just to scope it a bit away from the "real github action templating".
But it seems that is not possible?

I also thought introducing a class likepklGhaSettings { headerComment = "" }?! 🤔

An advice how to model this would be great.
Maybe having this as a templating property isn't that worth as I think it is?! 🤔