Null values in JSON BidRequest about openrtb HOT 4 CLOSED

Hum, that's painful... I was hoping that nobody would actually have messages with null values, even if they are valid in JSON (OpenRTB implementations are supposed to avoid redundancies like 'keywords: null' because it's good to make messages shorter)... it seems that was too optimistic.

I think the only good solution here will be to change the reader so it detects VALUE_NULL tokens and skips them (option 2). Investigating this now.

from openrtb.

Ok, I have implemented support for nulls, and also used the opportunity to make another pending refactoring that will make easier for people to customize the serialization of individual fields if necessary (see Issue 10). Can you check this at the fork https://github.com/opinali/openrtb, if it works for you I'll merge that here.

from openrtb.

that has resolved the issue. thanks 👍

from openrtb.

Good, merged as commit d3204c8.

from openrtb.