How to Effectively Structure and Reference Golang Modules in Different Directories?

How to Structure Golang Modules and Project Structure in the New Way

Referencing Modules from Different Directories

Since the introduction of modules in Go 1.11, the way modules are referenced and structured has changed significantly. To reference a module from a different directory, the following steps should be taken:

Old Way:

1. GOPATH Dependency: Ensure that the module is under GOPATH for it to be accessible.
2. Positioning: Place the module in the appropriate directory within GOPATH/src.
3. Importing: Use import statements to include the desired module.

New Way:

1. Module Initialization: Create new modules using go mod init.
2. go.mod File: Add the required dependencies to the go.mod file.
3. Relative Importing: Use relative import paths to reference the module within the project directory structure.

Example

Let's consider the following project structure:

\root
    \module1
        \go.mod
    \module2
        \go.mod

To reference module2 from module1, follow these steps:

1. Include github.com/your-username/module2 as a dependency in module1/go.mod.

2. Use a relative import path in module1 source code:

   import "./../module2"

Relative Importing

In the new module system, Go supports relative importing, allowing developers to reference modules relative to the current module's location. The syntax for relative importing is:

import "./relative/path/to/module"

This approach enables the separation of projects into modules while maintaining easy referencing between modules.

The above is the detailed content of How to Effectively Structure and Reference Golang Modules in Different Directories?. For more information, please follow other related articles on the PHP Chinese website!