Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JPATH not applied to --tla-code-file #130

Open
Duologic opened this issue Aug 28, 2023 · 1 comment · May be fixed by #135
Open

JPATH not applied to --tla-code-file #130

Duologic opened this issue Aug 28, 2023 · 1 comment · May be fixed by #135
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Duologic
Copy link

A plain example:

[I] ➜ cat vendor/read.jsonnet
{}

[I] ➜ jsonnet -J vendor --tla-code-file "file=read.jsonnet" -e 'function(file) std.toString(file)'
"{ }"

[I] ➜ jrsonnet -J vendor --tla-code-file "file=read.jsonnet" -e 'function(file) std.toString(file)'
error: invalid value 'file=read.jsonnet' for '--tla-code-file <name=tla code path>': No such file or directory (os error 2)

For more information, try '--help'.

I've also found that when using the full path vendor/<path/to/file> and the tla-code-file has relative imports it may not work well either, but couldn't come up with a minimally reproducible test case.

@JarvisCraft JarvisCraft added the bug Something isn't working label Aug 28, 2023
@JarvisCraft JarvisCraft added this to the v0.5.0 milestone Aug 28, 2023
@CertainLach
Copy link
Owner

Huh. I wonder why jpath is not resolved in input in official jsonnet, yet tla-code-file uses it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: To do
Development

Successfully merging a pull request may close this issue.

3 participants