Several bidders have made use of a Prebid.js feature called "transformBidParams" that maps client-side datatypes to server-side datatypes. This was useful because javascript is more forgiving about datatypes than the server-side adapters.
For example, at one point a couple years ago, the rubicon client-side adapter docs asked for strings, but the server-side adapter wanted integers. The docs were updated, but there may still be publishers using old params. Other bidders that do similar things include: ix, openx, openweb, and pubmatic.
I believe that the JSON schema can be made to allow multiple datatypes. If it does, then the easy solution here is to just update the server-side bid adapters to do any necessary conversions. I see evidence in PBS-Java that multiple datatypes are supported, but would like to confirm.
Several bidders have made use of a Prebid.js feature called "transformBidParams" that maps client-side datatypes to server-side datatypes. This was useful because javascript is more forgiving about datatypes than the server-side adapters.
For example, at one point a couple years ago, the rubicon client-side adapter docs asked for strings, but the server-side adapter wanted integers. The docs were updated, but there may still be publishers using old params. Other bidders that do similar things include: ix, openx, openweb, and pubmatic.
I believe that the JSON schema can be made to allow multiple datatypes. If it does, then the easy solution here is to just update the server-side bid adapters to do any necessary conversions. I see evidence in PBS-Java that multiple datatypes are supported, but would like to confirm.