Skip to content

Conversation

@przemkaczmarek
Copy link
Collaborator

🔧 Type of changes

  • bid adapter update

✨ What's the context?

#4199

@przemkaczmarek przemkaczmarek self-assigned this Oct 3, 2025
@AntoxaAntoxic AntoxaAntoxic linked an issue Oct 6, 2025 that may be closed by this pull request
String crId;

@JsonProperty("adomain")
List<String> adomain;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as I understand adomain is not an array, it's a plain text

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but in Go they treat it like array:
image
image

Copy link
Collaborator

@AntoxaAntoxic AntoxaAntoxic Oct 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

check the line 46 on your screenshot, the bidder literally returns the plain text, but the ortb2 response expects an array, so they set an array of a single element to the bid.adomain

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, and I just noticed that the the name should be adom instead of adomain, please fix that as well

@JsonProperty("crid")
String crId;

@JsonProperty("adomain")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the annotation is redundant


@JsonProperty("adomain")
List<String> adomain;
@JsonProperty()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove json property

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this field isn't needed, but all the other fields have it, and when I edit the adapter, I try to keep things consistent.

Copy link
Collaborator

@AntoxaAntoxic AntoxaAntoxic Oct 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The best practice here is not leaving a code that does nothing. Anyway all other fields have the @JsonProperty because they need them (maybe except for adM - I believe it's just a typo, so you can rename it to adm and remove the annotation as well)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noticed the name test-eplanning-bid-response-1.json ends with 1 which is confusing and weird, let's rename the file

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, but this is not a file made by me. It was already like that.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Always leave the code a little better than you found it" (c) The Boy Scout Rule

@CTMBNara CTMBNara merged commit 6ca71a7 into master Oct 21, 2025
8 checks passed
@CTMBNara CTMBNara deleted the Eplanning-Add-support-for-adomain branch October 21, 2025 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Port PR from PBS-Go: e-planning: Add support for adomain

4 participants