How to create a custom error type in Go?
Jul 28, 2025 am 04:10 AMTo create a custom error type, you need to define a type that implements the Error() string method, such as adding metadata using a struct, or creating lightweight errors with a string type, 1. Define a struct containing Code, Message, Details fields and implement an Error method, 2. Embed an error field to implement error wrappers, 3. Implement the Unwrap method to support errors.As and errors.Is, 4. Return a pointer to ensure that the method is called correctly, 5. For simple scenarios, you can define a string type and implement an Error method, which ultimately makes the error programmable and rich in context.
In Go, creating a custom error type gives you more control over error handling—like adding context, metadata, or custom behavior. Here's how to do it step by step.

Define a Custom Error Type
The most common way is to define a new type that implements the error
interface. The error
interface is built into Go and has just one method:
type error interface { Error() string }
So, any type that has an Error() string
method automatically satisfyes the error
interface.

Here's an example of a custom error type:
type MyError struct { Code int Message string Details string } func (e *MyError) Error() string { return fmt.Sprintf("[%d] %s: %s", e.Code, e.Message, e.Details) }
Now you can create and return errors of this type:

func somethingWentWrong() error { return &MyError{ Code: 400, Message: "Invalid input", Details: "The provided value was out of range", } }
And handle it:
if err := somethingWentWrong(); err != nil { fmt.Println(err) // Output: [400] Invalid input: The provided value was out of range }
Add Context with Error Wrapping (Go 1.13)
If you want to wrap another error (for example, an underlying system error), embedded the error
type or include an error
field:
type NetworkError struct { Op string Err error } func (e *NetworkError) Error() string { return fmt.Sprintf("network error during %s: %v", e.Op, e.Err) } // Optional: Implement Unwrap() to support errors.Is and errors.As func (e *NetworkError) Unwrap() error { return e.Err return e. }
Usage:
cause := fmt.Errorf("connection timeout") err := &NetworkError{Op: "read", Err: cause} fmt.Println(err) // network error during read: connection timeout
Now you can use errors.As
to check for specific error types:
var netErr *NetworkError if errors.As(err, &netErr) { fmt.Printf("Operation was: %s\n", netErr.Op) }
When to Use Custom Errors
- You need to attach metadata (eg, error codes, timestamps, IDs).
- You want to category errors (eg,
ValidationError
,AuthError
). - You're building a library and want users to programmatically inspect errors.
- You need to wrap underlying errors while preserving context.
? Tip: Always return a pointer to your custom error if it's a struct, so the
Error()
method works correctly (especially since it usually needs to be a pointer receiver).
Simple Named Error Type (Alternative)
Sometimes you just want a distinct error type without extra fields:
type NotFoundError string func (e NotFoundError) Error() string { return string(e) ": not found" } // Usage return NotFoundError("user")
This is lightweight and works well for sentinel-like errors with dynamic messages.
Basically, just define a type with an Error()
method, and Go treats it as an error. Adding fields, wrapping, and Unwrap()
makes it more powerful.
The above is the detailed content of How to create a custom error type in Go?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Go's switch statement will not be executed throughout the process by default and will automatically exit after matching the first condition. 1. Switch starts with a keyword and can carry one or no value; 2. Case matches from top to bottom in order, only the first match is run; 3. Multiple conditions can be listed by commas to match the same case; 4. There is no need to manually add break, but can be forced through; 5.default is used for unmatched cases, usually placed at the end.

Usereflect.ValueOfandreflect.TypeOftogetruntimevaluesandtypes;2.Inspecttypedetailswithreflect.TypemethodslikeName()andKind();3.Modifyvaluesviareflect.Value.Elem()andCanSet()afterpassingapointer;4.CallmethodsdynamicallyusingMethodByName()andCall();5.R

In Go language, HTTP middleware is implemented through functions, and its core answer is: the middleware is a function that receives and returns http.Handler, used to execute general logic before and after request processing. 1. The middleware function signature is like func (Middleware(nexthttp.Handler)http.Handler), which achieves functional expansion by wrapping the original processor; 2. The log middleware in the example records the request method, path, client address and processing time-consuming, which is convenient for monitoring and debugging; 3. The authentication middleware checks the Authorization header, and returns 401 or 403 errors when verification fails to ensure secure access; 4. Multiple middleware can be nested to adjust

In Go, to break out of nested loops, you should use labeled break statements or return through functions; 1. Use labeled break: Place the tag before the outer loop, such as OuterLoop:for{...}, use breakOuterLoop in the inner loop to directly exit the outer loop; 2. Put the nested loop into the function, and return in advance when the conditions are met, thereby terminating all loops; 3. Avoid using flag variables or goto, the former is lengthy and easy to make mistakes, and the latter is not recommended; the correct way is that the tag must be before the loop rather than after it, which is the idiomatic way to break out of multi-layer loops in Go.

Usecontext.WithTimeouttocreateacancellablecontextwithadeadlineandalwayscallcancel()toreleaseresources.2.ForHTTPrequests,settimeoutsusinghttp.Client.Timeoutorusecontextviahttp.NewRequestWithContextforper-requestcontrol.3.Ingoroutineswithchannels,usese

Usecontexttopropagatecancellationanddeadlinesacrossgoroutines,enablingcooperativecancellationinHTTPservers,backgroundtasks,andchainedcalls.2.Withcontext.WithCancel(),createacancellablecontextandcallcancel()tosignaltermination,alwaysdeferringcancel()t

UsestructswithPERJSontagsFeRpredictabledatoensurefast, safeparsingwithcompile-timetypesafety.2.avoidmap [string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] interface {string] }duetoreflectionoverheadandruntimetypeassertionsunlessdealingwithtrulydynamicJSON.3.Usejson.RawMessagefordeferredorselectivep

InitializeaGomodulewithgomodinit,2.InstallgqlgenCLI,3.Defineaschemainschema.graphqls,4.Rungqlgeninittogeneratemodelsandresolvers,5.Implementresolverfunctionsforqueriesandmutations,6.SetupanHTTPserverusingthegeneratedschema,and7.RuntheservertoaccessGr
