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
I'd like to be able to set the --jsonnetpkg-home for jsonnet-bundler, as the vendor directory conflicts with go vendoring, I want to use jsonnet-vendor instead.
The text was updated successfully, but these errors were encountered:
ghostsquad
added a commit
to ghostsquad/currency-converter-practice
that referenced
this issue
Mar 12, 2023
go and jsonnet/jb/tanka fight over the `vendor` directory. This is somewhat fixed with `-mod=readonly` or `-mod=mod` as an explicit flag to go commands, or `GOFLAGS=-mod=mod`, however, Jetbrains GOLAND still has problems if the `vendor` directory exists and doesn't have go files in it. See https://youtrack.jetbrains.com/issue/GO-10952/No-way-to-disable-vendoring-for-Sync-Dependencies-quick-fix. To get Goland to not freak out, `rm -rfd vendor`. This of course breaks all the Jsonnet, so when you are ready to do anything else, run `task jb:install`.
Another possible way to fix this is if tanka supported other vendor directories. See grafana/tanka#356 and grafana/tanka#820.
I'd like to be able to set the
--jsonnetpkg-home
for jsonnet-bundler, as thevendor
directory conflicts with go vendoring, I want to usejsonnet-vendor
instead.The text was updated successfully, but these errors were encountered: