How to do functional options in Golang

functional-options.md

Here's the simplest example showing how to do functional options in Golang.

They're a great way to enable users to set options and ease adding new options later.

package main

import (
	"flag"
	"fmt"
)

// This is your function used by users to set options.
func Host(host string) func(*Server) {
	return func(s *Server) {
		s.Host = host
	}
}

// This is another function used by users to set options.
func Port(port int) func(*Server) {
	return func(s *Server) {
		s.Port = port
	}
}

// This is the type whose options you're enabling users to set.
type Server struct {
	Host string
	Port int
}

// This is your creator function that accepts a list of option functions.
func NewServer(opts ...func(*Server)) *Server {
	s := &Server{}

	// call option functions on instance to set options on it
	for _, opt := range opts {
		opt(s)
	}

	return s
}

func main() {
	var host = flag.String("host", "127.0.0.1", "host")
	var port = flag.Int("port", 8000, "port")
	flag.Parse()

	// This is how your user sets the options.
	s := NewServer(
		Host(*host),
		Port(*port),
	)

	fmt.Printf("server host: %s, port: %d", s.Host, s.Port)
}

What if I need to validate some parameters? For example, I want to check Port is > 0 && < 10000. How should I do error handling in such case?

@melekes to tackle validations, you'll want to change your function option signature to return an error and use that for validation purposes

for example

package main

import (
	"flag"
	"fmt"
)

type ErrPortInvalid struct {
	portValue int
}

func(e ErrPortInvalid) Error() string {
	return fmt.Sprintf("supplied port %d must be between 0 and 10000", e.value)
}

// The option is now a function that takes a pointer to a Server and returns an error if it is invalid
type option func(*Server) error

// This is your function used by users to set options.
// For this option, perform no validations.
func Host(host string) option {
	return func(s *Server) error {
		s.Host = host
                return nil
	}
}

// This is another function used by users to set options.
// For this option, validate that it is between 0 and 10000 exclusively.
func Port(port int) option {
	return func(s *Server) error {
		if port <= 0 || 10000 <= port {
			return ErrPortInvalid{port}
		}
                s.Port = port
		return nil
	}
}

// This is the type whose options you're enabling users to set.
type Server struct {
	Host string
	Port int
}

// This is your creator function that accepts a list of option functions.
func NewServer(opts ...option) (*Server, []error) {
	s := &Server{}
	errs := make([]error, 0)

	// call option functions on instance to set options on it
	for _, opt := range opts {
		err := opt(s)
		// if the option func returns an error, add it to the list of errors
		if err != nil {
			errs = append(errs, err)
		}
	}

	return s, errs
}

func main() {
	var host = flag.String("host", "127.0.0.1", "host")
	var port = flag.Int("port", 8000, "port")
	flag.Parse()

	// This is how your user sets the options.
	s, _ := NewServer(
		Host(*host),
		Port(*port),
	)

	fmt.Printf("server host: %s, port: %d\n", s.Host, s.Port)
	
	// If the user supplies an invalid port
	invalidPort := 10001
	_, errs := NewServer(
		Host(*host),
		Port(invalidPort),
	)
	// errs will be the list of validation errors
	if len(errs) > 0 {
		fmt.Println("invalid server config", errs)
	}
}

Cool! Thank you

So much boilerplate for something so simple. It's quite ridiculous. Google says they do it to avoid bad practices but instead they open pandoras box of bad practices with a restriction like this because now everyone comes up with their own ad hoc solution. It makes code potentially unreadable and forces developers to get creative. The exact opposite of go's goals.

I'm sure they will add some proper sane syntax for optional parameters at some point.

By the way not only is this 'solution' extremely verbose, it's also far from perfect. I.e. you can specify multiple Ports and Hosts. You can also set those parameters after initialization which is not exactly what you want for a Server.

Sorry for that totally off-topic rant but maybe those are necessary.

My final solution https://gist.github.com/logrusorgru/0d0f4ac5d7b95f79b7884b5664658bc9#gistcomment-3655344 Thanks!