These guidelines for writing Go code are WIP
This document covers common coding styles and guidelines for all ForgeRock products.
Within the FRaaS codebases we are not currently adding licence headers to individual source files. This practice diverges from the standard practice of doing so across other projects.
The ForgeRock Go coding style
- Each Go project should include one or more README.md files detailing
- An overview of the project and its purpose
- How to build, test, deploy and configure the executable
- All public constants, structs, fields, interfaces and functions must have Go doc
- All packages must have Go doc - Packages with more than one source file should consider providing package documentation using a doc.go file
Source code layout
In addition to good documentation, having a consistent approach to organising code across directories and within a given source file makes it easier for engineers to move between projects and get up to speed quickly.
- Each Go project should use a standard layout
- Each Go source file should, as far as possible, be readable top-to-bottom with public / high level functions at the top of source files and private / helper functions lower down:
- public functions
- private functions
Where possible, agreed standards relating to source files should be enforced by linting during continuous integration. The linting rules currently in use by the FRaaS team are:
- Avoid logging directly at the site where an error is produced or returned. Instead let the entry point to processing do the logging. If the returned error message is insufficient (often they are already sufficient) use
errors.Wrapto add context to the returned error.
- Use the
github.com/pkg/errorspackage instead of
errors, and user
errors.WithStack(err)wherever an error is produced or returned from an external package.
WithStackproduces a stack trace pointing to the line of code which produced the error, which also prevents us from having to add our own custom error message so that we can correlate the error message to the line of code which produced it.This can also be done wherever there's an
Any new packages that need to log things should use the common logger specified in common/pkg/logging/logging.go. This can be used by importing in your package (in package.go, or another file)
Programs should only exit in a 'main' function, and should log which error caused the program to fail at the 'Fatal' level. This will make it obvious when looking at logs where and why the program exited.
In addition to the points raised above, we should endeavour to write idiomatic Go. Guidance for what these idioms are and how to follow them can be found in:
When adding a new interface that will require a mock there are a few simple steps to follow
- Follow the instructions to install mockery
- Add a line either above the interface you've added or in a package.go file alongside the interface with a 'go generate' comment
- Run 'go generate ./...' in the relevant folder - this will run 'mockery' and generate a mock for your interface under the 'mocks' folder
Your interface should look like this:
If you need to generate a mock for an interface but you also need to use that mock in the same package, this will cause import cycles. To get around this, add '--inpackage' to the list of arguments to 'mockery' in the generate comment.
If you want to use one of these mocks in one of your tests, there is a small utility function in go/common/pkg/testutil/mockhelper.go which can be used to do some common setup and mock assertion. An example of how to use this:
The testify documentation will have more information about what methods these mocks will have and how to use them.
Commonly used libraries
- (Pending review and approval from others) Validator validates struct data to ensure input matches what's required. github.com/go-playground/validator