Open rprimet opened 1 week ago
This is indeed a limitation of Ninja: the "key" identifying a target is a specific PATH, without resolution of the underlying file of any kind. I admit it's a sane default though.
What we could attempt to do is some resolution of file names specified on the command-line before we call Ninja from Clerk, though.
Hi,
Not sure whether it's a bug, just a behavior that I would like more context on and possibly a discussion? : running
clerk run
with a file yields a different behavior when the target file path is absolute or relative.For instance, in
catala-language-server
:(absolute path)
(relative path)
(if that matters, the
clerk.toml
file is in theexamples
direcory in this instance)