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

go.mod content error #264

Closed
VoSiqiino opened this issue Apr 14, 2024 · 3 comments · Fixed by #268
Closed

go.mod content error #264

VoSiqiino opened this issue Apr 14, 2024 · 3 comments · Fixed by #268

Comments

@VoSiqiino
Copy link

module go.einride.tech/can

should be

module github.com/einride/can-go

@alethenorio
Copy link
Contributor

Thank you for the issue. This repository uses what is called a Vanity URL so go.einride.tech/can is indeed the correct module name.

@Jassob
Copy link
Member

Jassob commented May 2, 2024

But maybe we should add a MWE in README.md to show that the import path is indeed go.einride.tech/can?

@alethenorio
Copy link
Contributor

@Jassob good idea

Jassob added a commit that referenced this issue May 6, 2024
We received an issue (#264) about having the wrong module path in
go.mod. This commit aims to resolve the issue by making it clearer.

Fixes #264.
Jassob added a commit that referenced this issue May 6, 2024
We received an issue (#264) about having the wrong module path in
go.mod. This commit aims to resolve the issue by making it clearer.

Fixes #264.
Jassob added a commit that referenced this issue May 6, 2024
We received an issue (#264) about having the wrong module path in
go.mod. This commit aims to resolve the issue by making it clearer.

Fixes #264.
Jassob added a commit that referenced this issue May 16, 2024
We received an issue (#264) about having the wrong module path in
go.mod. This commit aims to resolve the issue by making it clearer.

Fixes #264.
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 a pull request may close this issue.

3 participants