openrtb

OpenRTB, AdCOM and OpenRTB Dynamic Native Ads types for Go programming language
Requires Go 1.13+
This library is switched to Go modules (tl;dr) as of v14.0.0, so it requires Go 1.11+ (older Go versions are not capable of using versioned paths).
Also, test/matcher library relies on newer Go error handling approach, so tests require Go 1.13+.
Using
go get -u "github.com/mxmCherry/openrtb/v16/..."
import (
openrtb2 "github.com/mxmCherry/openrtb/v16/openrtb2"
openrtb3 "github.com/mxmCherry/openrtb/v16/openrtb3"
adcom1 "github.com/mxmCherry/openrtb/v16/adcom1"
native1 "github.com/mxmCherry/openrtb/v16/native1"
nreq "github.com/mxmCherry/openrtb/v16/native1/request"
nres "github.com/mxmCherry/openrtb/v16/native1/response"
)
This repo follows semver - see releases.
Master always contains latest code, so better use some package manager to vendor specific version.
Guidelines
Naming convention
- UpperCamelCase
- Capitalized abbreviations (e.g.,
AT, COPPA, PMP etc.)
- Capitalized
ID keys
- Enum items with versions should include minor/patch zeros, i.e. "Foo 1.0" ->
Foo10 (and not just Foo1), "Foo 1.1" -> Foo11 etc
Types
- Key types should be chosen according to OpenRTB specification (attribute types)
- Numeric types:
int8 - short enums (with values <= 127), boolean-like attributes (like BidRequest.test)
int64 - other integral types
float64 - coordinates, prices etc.
- Enums:
- all enums, described in section 5, must be typed with section name singularized (e.g., "5.2 Banner Ad Types" ->
type BannerAdType int8)
- all typed enums must have constants for each element, prefixed with type name (e.g., "5.2 Banner Ad Types - XHTML Text Ad (usually mobile)" ->
const BannerAdTypeXHTMLTextAd BannerAdType = 1)
- never use
iota for enum constants
- OpenRTB (2.x) section "5.1 Content Categories" should remain untyped and have no constants
Pointers/omitempty
| Pointer |
Omitempty |
When to use |
Example |
| no |
no |
required in spec |
Audio.mimes |
| yes |
yes |
required in spec, but is a part of mutually-exclusive group |
Imp.{banner,video,audio,native} |
| no |
yes |
zero value ("", 0) is useless / has no meaning |
Device.ua |
| yes |
yes |
zero value ("", 0) or value absence (null) has special meaning |
Device.{dnt,lmt} |
Using both pointer and omitempty is mostly just to save traffic / generate more "canonical" (strict) JSON.
- Godoc: documenting Go code
- Each entity (type, struct key or constant) should be documented
- Ideally, copy-paste descriptions as-is, but feel free to omit section numbers, so just
<GoTypeName> defines <copy-pasted description from spec>
Code organization
- Each RTB type should be kept in its own file, named after type
- File names are in underscore_case, e.g.,
type BidRequest should be declared in bid_request.go
- go fmt your code
- EditorConfig (not required, but useful)