Should you try w.Submodule(name) first before checking the Paths?

I'm thinking that in this case, the "name" variable should actually be the path. So, in order to avoid the situation where the name of the submodule happens to match the path while the path itself fails to match properly, perhaps the "Submodule(name)" method shouldn't be attempted here.

If that is indeed the case (I haven't looked at the code or the calling code) then the parameter name is wrong, you should rename it.

The related methods are all using "name" as the variable name. I'm not sure whether it's appropriate to modify it. It seems that "name" represents the file name (and path), and there is ambiguity when dealing with submodules.

The existing code looks up for the submodule by name: m.Config().Name == name. This current change does not seem backwards compatible, as although in some cases name and path may be the same, I am not sure that is a hard rule.

I'd keep the existing check (i.e. w.Submodule(name)), and if the submodule was not found, then try to get it by path (e.g. by calling a new func w.submoduleByPath(path)).