You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, evaluation of a Pkl module with multi-file output ignores the output format parameter for the pkl eval call (or the outputFormat property in case of the Gradle plugin). For example (snippet taken from the docs):
// birds.pklpigeon {
name = "Pigeon"diet = "Seeds"
}
parrot {
name = "Parrot"diet = "Seeds"
}
output {
files {
["birds/pigeon.out"] {
value = pigeon
}
["birds/parrot.out"] {
value = parrot
}
}
}
This is different from the regular single-file output mode, where -f would determine the default renderer in case it is not explicitly specified.
It would probably make sense for the -f argument to be honored for multi-file output as well, in the same way as for single-file output - by determining the output format in case an explicit renderer is not defined.
The text was updated successfully, but these errors were encountered:
Currently, evaluation of a Pkl module with multi-file output ignores the output format parameter for the
pkl eval
call (or theoutputFormat
property in case of the Gradle plugin). For example (snippet taken from the docs):This is different from the regular single-file output mode, where
-f
would determine the default renderer in case it is not explicitly specified.It would probably make sense for the
-f
argument to be honored for multi-file output as well, in the same way as for single-file output - by determining the output format in case an explicit renderer is not defined.The text was updated successfully, but these errors were encountered: