commit | 19d50cac98aa7a8e0a0c8b6a9bfd3a99e653c0cc | [log] [tgz] |
---|---|---|
author | Jay Conrod <jayconrod@google.com> | Tue Mar 02 11:48:48 2021 -0500 |
committer | Jay Conrod <jayconrod@google.com> | Wed Mar 10 18:58:34 2021 +0000 |
tree | 705f1f73b02b5fc42eef92f26581e3a1fc8f7774 | |
parent | d6ab96f2441f9631f81862375ef66782fc4a9c12 [diff] |
module: add InvalidPathError CheckPath, CheckImportPath, and CheckFilePath now return this error. To be used in CL 297634. Change-Id: Ibc4af7c5593f35216ab3ade0b024971061b8cf97 Reviewed-on: https://go-review.googlesource.com/c/mod/+/297891 Trust: Jay Conrod <jayconrod@google.com> Run-TryBot: Jay Conrod <jayconrod@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.