Handle incoming bool/int fields for lgpd

numbers.go

@@ -2,6 +2,7 @@ package openrtb
 
 import (
 	"encoding/json"
+	"errors"
 	"strconv"
 )
 
@@ -51,3 +52,27 @@ func (n *StringOrNumber) UnmarshalJSON(data []byte) error {
 	}
 	return nil
 }
+
+// BoolOrNumber attemps to fix OpenRTB incompatibilities where a field is expected as bool but the spec expects int values. This was not seen till now, but some mediation partners will follow the spec closely.
+type BoolOrNumber bool
+
+// UnmarshalJSON implements json.Unmarshaler
+func (b *BoolOrNumber) UnmarshalJSON(data []byte) error {
+	var val interface{}
+	if err := json.Unmarshal(data, &val); err != nil {
+		return err
+	}
+
+	switch v := val.(type) {
+	case bool:
+		*b = BoolOrNumber(v)
+	case float64:
+		// When unmarshaling JSON into an interface value, Unmarshal stores JSON numbers in the interface value float64
+		*b = BoolOrNumber(v != 0)
+	default:
+
+		return errors.New("BoolOrInt: invalid type")
+	}
+
+	return nil
+}

openrtb.go

@@ -841,10 +841,10 @@ type ChannelEntity struct {
 
 // RegExtension Extension object for Regulations
 type RegExtension struct {
-	GDPR      int    `json:"gdpr,omitempty"`
-	LGPD      bool   `json:"lgpd,omitempty"`
-	PIPL      bool   `json:"pipl,omitempty"`
-	USPrivacy string `json:"us_privacy,omitempty"`
+	GDPR      int          `json:"gdpr,omitempty"`
+	LGPD      BoolOrNumber `json:"lgpd,omitempty"`
+	PIPL      BoolOrNumber `json:"pipl,omitempty"`
+	USPrivacy string       `json:"us_privacy,omitempty"`
 }
 
 // UserExtension Extension object for User