-
Hi All I'm using Pkl as part of a go project that will run on multiple machines, as such it has additional custom config that is read from the file by the app and then evaluated as a text source in Pkl. To prevent the same class being written multiple times as the configuration will be a standard layout each time, I planned to import it from another Pkl file. I achieved this by having my go app insert this import line before the rest of the string containing all the pkl configuration, however despite it being an absolute path on my system, it is still rejected with this message.
Is this by design? It'd be great if we can still take advantage of importing in a text based source, especially if it's an absolute path on the system. Happy to share more details and implementation if needed. Thanks :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This works; you just need to prepend
|
Beta Was this translation helpful? Give feedback.
This works; you just need to prepend
file://
to the filename: