How to Access Modules Across Different Directories in a Revised Go Project Structure?

Accessing Modules in a Revised Golang Project Structure

Since Go version 1.11, module management has undergone significant changes. To understand how to reference a module from a different directory in the new project structure, let's examine your folder setup:

\root\module1
\root\module2

Each directory contains a go.mod file, and you can successfully access these modules in the root directory. However, to access module2 from module1, follow these steps:

OLD WAY

In the traditional approach, modules must be placed in the GOPATH environment variable to be accessible. The GOPATH folder usually has the following structure:

$GOPATH
├── bin
├── pkg
└── src
   ├── github.com
   └── other_imported_modules

You can import a data structure file named datastructures.go from module2 in module1 using the import statement:

import (
    "github.ibm.com/Alessio-Savi/GoLog-Viewer/datastructure"
)

NEW WAY

The modern approach to module management involves using the go mod init command:

go mod init github.com/username/modulename

This generates go.mod and go.sum files. The go.mod file contains dependencies, while go.sum stores their hashes. For example, your go.mod file for module2 might look like:

module github.com/username/module2

go 1.13

require (
    github.com/alessiosavi/ahocorasick v0.0.3
)

Now, you can import module2 in module1:

import (
    "github.com/username/module2"
)

This method allows you to access your modules without having to publish them or place them in the GOPATH.

The above is the detailed content of How to Access Modules Across Different Directories in a Revised Go Project Structure?. For more information, please follow other related articles on the PHP Chinese website!