-
-
Notifications
You must be signed in to change notification settings - Fork 571
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
fix(gazelle): Use dougthor42's go-tree-sitter
via replace
instead of modifying names
#2667
base: main
Are you sure you want to change the base?
fix(gazelle): Use dougthor42's go-tree-sitter
via replace
instead of modifying names
#2667
Conversation
That looks right, but the CI error seems to be the "fatal error: ../array.h: No such file or directory" error which required the custom BUILD files? Yet only bzlmod is failing? :/ |
The issue is that go.mod
So while the |
So this solution won't work? There must be another way to do this other then today's solution 😢 |
@dougthor42 how about adding to the default_gazelle_overrides.bzl. I've never investigated it before so I'm not entirely sure if that's right, and it seems to be in a "bzlmod" directory. Can we just contribute to that file to get gazelle properly generating BUILDs for |
Fixes #2630.
In #2496 we added support for Python 3.12 syntax using the less-than-ideal method of "fork and rename everything". This turned out to be a Bad Idea ™️ for people who happened to be using
smacker/go-tree-sitter
as a direct dependency.This PR effectively reverts #2496 and replaces it with a more correct way of doing go module forking: the
replace
directive forgo.mod
.Special thanks goes out to @jbedard for raising the issue and for continuing to poke me to fix it!
If we look at #2496 plus this PR, the net diff to get Python 3.12 support is approximately1:
Footnotes
Manually generated; ignores the Python 3.12 test ↩