This is a pretty minor thing, but I figured I’d ask about it anyway.
In VS Code, when working on code in a package, I can command-click on a function call and be taken to its definition (although if there are multiple methods with the same name, it can’t figure out which one is being called, but in practice it works decently well).
However, if I’m working on that package’s unit tests, navigation to a package function is unavailable, so I generally need to go use the text search to locate methods. Is there some way to get this navigation working in this common use case?
Interesting! I do already have a Project.toml in my tests folder, but I think I’ll use option 2, because that seems like it will “just work” for new developers, but option 1 would need them all to dev the project individually (unless I check in the Manifest.toml, which I think I don’t want to do), right?
in test/Project.toml, where PackageName is the name of your package. This works in Julia >= 1.11, which is probably what new developers would be using.
Oh indeed, that seems to be working - “delete the Manifest.toml” isn’t normally in my repertoire, I think I was trying to use resolve and/or instantiate within the REPL, I don’t remember exactly how, but clearly it wasn’t working.
Yes, it is somewhat annoying that sometimes you have to delete the manifest file manually, and that Julia (or Pkg?) cannot figure out that this might be needed itself. At least Julia or Pkg should give a hint in such a situation that this might be needed.