Go
Requirements
This module requires Go version >= 1.13.
Installation
Run the following command to use the Mercoa Go library in your module:
Usage
Optionals
This library models optional primitives and enum types as pointers. This is primarily meant to distinguish
default zero values from explicit values (e.g. false
for bool
and ""
for string
). A collection of
helper functions are provided to easily map a primitive or enum to its pointer-equivalent (e.g. mercoa.Int
).
For example, consider the client.Entity.Find
endpoint usage below:
Timeouts
Setting a timeout for each individual request is as simple as using the standard
context
library. Setting a one second timeout for an individual API call looks
like the following:
Request Options
A variety of request options are included to adapt the behavior of the library, which includes
configuring authorization tokens, or providing your own instrumented *http.Client
. Both of
these options are shown below:
These request options can either be specified on the client so that they’re applied on every request (shown above), or for an individual request like so:
Providing your own
*http.Client
is recommended. Otherwise, thehttp.DefaultClient
will be used, and your client will wait indefinitely for a response (unless the per-request, context-based timeout is used).
Automatic Retries
The Mercoa Go client is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retriable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retriable when any of the following HTTP status codes is returned:
You can use the option.WithMaxAttempts
option to configure the maximum retry limit to
your liking. For example, if you want to disable retries for the client entirely, you can
set this value to 1 like so:
This can be done for an individual request, too:
Errors
Structured error types are returned from API calls that return non-success status codes. For example, you can check if the error was due to a bad request (i.e. status code 400) with the following:
These errors are also compatible with the errors.Is
and errors.As
APIs, so you can access the error
like so:
If you’d like to wrap the errors with additional information and still retain the ability
to access the type with errors.Is
and errors.As
, you can use the %w
directive: