Pre-defined native types: Image not replaced before adapters are called

[guiann]

Hello everyone,

Our bidder supports native ads for a few weeks now and we can see some native bid format with

native: {
    type: "image"
}

I would expect this native configuration to be replaced by the full format config specified in:
pre-defined-native-types

{
    image: { required: true },
    title: { required: true },
    sponsoredBy: { required: true },
    clickUrl: { required: true },
    body: { required: false },
    icon: { required: false },
    cta: { required: false }
}

Is it expected that bidder adapters receive the short hand format?
That would mean every bidder has to expand every pre-defined types. Duplicating the same code for every bidder and breaking futur integrations when new pre-formated types will be added.

[gglas]

@aleksatr @robertrmartinez We discussed this on issue review today, and this seems like a good place to introduce the concept of prebid Native templates with predefined requirements that are then accessed via Shorthand. Aleksa I tagged you until we can add Chris N to prebid, I think he'd find this interesting.

[patmmccann]

@guiann this expansion of the shorthand inside of core seems like a great utils function for all adapters accepting native; is there any chance you could take a stab at the function?

[guiann]

No I've no time to handle it sorry.

[dgirardi]

Core now makes the "expanded" type available under bidRequest.nativeParams:

Prebid.js/src/native.js

Lines 39 to 47 in 0d3f875

	export function decorateAdUnitsWithNativeParams(adUnits) {
	adUnits.forEach(adUnit => {
	const nativeParams =
	adUnit.nativeParams || deepAccess(adUnit, 'mediaTypes.native');
	if (nativeParams) {
	adUnit.nativeParams = processNativeAdUnitParams(nativeParams);
	}
	});
	}

Does that solve this issue?

[patmmccann]

Seems to