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

Fix go.mod name #7756

Merged
merged 1 commit into from
Jan 4, 2023
Merged

Fix go.mod name #7756

merged 1 commit into from
Jan 4, 2023

Conversation

le-michael
Copy link
Collaborator

Fixes go.mod naming issue introduced by #7720.

Module name should be github.com/google/flatbuffers/go not github.com/google/flatbuffers.

https://pkg.go.dev/github.com/google/flatbuffers/go
https://google.github.io/flatbuffers/flatbuffers_guide_use_go.html

@le-michael le-michael mentioned this pull request Jan 4, 2023
@dbaileychess dbaileychess merged commit 3b2eb77 into google:master Jan 4, 2023
frc971-automation pushed a commit to frc971/971-Robot-Code that referenced this pull request Jan 8, 2023
I don't understand exactly what's going on with the Go package
mirroring. For some reason gazelle doesn't want to mirror the
flatbuffers package. Possibly because we already have it defined in
our workspace. Not sure. There's some magic somewhere that I don't
have insight into. Regardless, we should explicitly point gazelle at
our vendored version of flatbuffers. That's what this patch
accomplishes.

I think this was caused by
google/flatbuffers#7756 or
google/flatbuffers#7720, but I'm not sure. At
least the timing matches.

This patch effectively reverts
Ibd850b77987625d359a38bf53d7db4ae9bc77dc2.

Signed-off-by: Philipp Schrader <philipp.schrader@gmail.com>
Change-Id: I489d2150811bd00ab810a3038bbac2d0dc74ff6d
sunwen18 pushed a commit to sunwen18/flatbuffers that referenced this pull request Jan 9, 2023
jochenparm pushed a commit to jochenparm/flatbuffers that referenced this pull request Oct 29, 2024
jochenparm pushed a commit to jochenparm/flatbuffers that referenced this pull request Oct 29, 2024
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.

2 participants