outdated import paths still reference github.com/MarioCarrion/todo-api

[computerscienceiscool]

The repository contains multiple outdated references to github.com/MarioCarrion/todo-api, but the actual module path is github.com/MarioCarrion/todo-api-microservice-example.

steps to reproduce:
1.
git clone https://github.com/MarioCarrion/todo-api-microservice-example.git
cd todo-api-microservice-example

Run go mod tidy:
go mod tidy

Errors received:
go: finding module for package github.com/MarioCarrion/todo-api/cmd/internal
fatal: repository 'https://github.com/MarioCarrion/todo-api/' not found

[computerscienceiscool]

I accessed this code while trying to complete the Software Architecture in Golang: C4 Model for Diagraming and Documentation video
https://www.youtube.com/watch?v=pZ2z2tZkMsE

[MarioCarrion]

Hi @computerscienceiscool 👋🏽

I can't reproduce it:

Not sure if this related to the Go version you're using, but either way I agree the Go module should match the actual repo URI as a best practice, I forgot to do that when I renamed this repository back in the day.

I created a new branch called rename-module, can you give it a try?

git clone https://github.com/MarioCarrion/todo-api-microservice-example.git
cd todo-api-microservice-example
git branch rename-module origin/rename-module
git checkout rename-module
make lint

LMK if that works. Cheers.

[computerscienceiscool]

At the time, I was trying to go through the C4 Model for Diagramming and Documentation video https://www.youtube.com/watch?v=pZ2z2tZkMsE

I was using 1.22.1, since that is my default, then I updated it to 1.23.5 to use your code
I am using goenv since I need to do things in different go versions.

[MarioCarrion]

@computerscienceiscool did the branch work for you? or did you figure it out on your own?

Also keep in mind tools like goenv are no longer needed since 1.21, the toolchain transparently deals with higher minor versions using go.mod.

[stevegt]

Hey Mario!

I'm working with @computerscienceiscool on an open-source project which to date has always used goenv as part of our dev environment. As far as I can tell, it's possible that we're running into outright incompatibilities between goenv and the newer GOTOOLCHAIN machinery. She and I both greatly appreciate your responsiveness on this so far; if nothing else you've given us a huge wakeup call on the new toolchain and our use cases. (I was one of the contributors to goenv, so this concerns me in other ways too.)

Because we need to sort out the new toolchain usage on our end, we, too, are also unable to duplicate the problem ourselves. We wanted to let you know that, and to let you know that you might want to hold off on merging rename-module unless you're able to test it to your own satisfaction without our silly help -- we've got some cleanup work to do, looks like.

For other lurkers who might stumble across this discussion later: Be aware that if you are using goenv, and are also using a version of Go >= 1.21, the go toolchain may override your Go version based on what is in the go directive in go.mod. (And as a goenv contributor myself, as of this writing, I can't even tell you if that override is complete -- you may in fact find yourself using a mixed set of bits from two different Go versions, which could of course cause all sorts of weird issues -- I need to suss this out myself.)

Steve

[MarioCarrion]

Hey Steve! Thanks for the context.

I tested the new branch and merged it to main; it seems to be working ok.

Please get in touch with me with other questions regarding this repo; I am happy to help.

Cheers!