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

Don't depend on go-jsonnet twice #204

Merged
merged 1 commit into from
Mar 29, 2024
Merged

Conversation

EdSchouten
Copy link
Member

It looks like we're currently both importing it as a module, and dragging it in through Gazelle. Let's only do the former. This does require us to put a 'gazelle:resolve' in BUILD.bazel to rewrite the Go package name for go-jsonnet to what's offered by the module.

It looks like we're currently both importing it as a module, and
dragging it in through Gazelle. Let's only do the former. This does
require us to put a 'gazelle:resolve' in BUILD.bazel to rewrite the Go
package name for go-jsonnet to what's offered by the module.
@EdSchouten EdSchouten merged commit 2c0ea99 into master Mar 29, 2024
1 check passed
@EdSchouten EdSchouten deleted the eschouten/20240329-go-jsonnet branch March 29, 2024 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant