package.json vs package-request.json in the media buy process

[marekjalovec]

core/package.json defines impressions field which is defined as the following:

    "impressions": {
      "type": "number",
      "description": "Impression goal for this package",
      "minimum": 0
    },

This is inconsistent with media-buy/package-request.json and media-buy/update-media-buy-request.json as neither of these define the impressions, so it's impossible to set this value for media buy packages.

---

Further inconsistencies worth considering:

• format_ids in media-buy/package-request.json vs format_ids_to_provide in code/package.json (this one might be intentional?)
• missing paused in media-buy/package-request.json, so it always defaults to false as per core/package.json definition without an option to set it initially

[BaiyuScope3]

Here is the fix for it:

• AdCP protocol: fix: Add missing impressions and paused fields to package request schemas #756
• AdCP client update for python and typescript will be post after above being merged
• Post Fix Actions: the new fixed schema will be present after upgrading adcp client version used in the agent (version number will be provided later)

Thanks for catching it @marekjalovec 👍

[BaiyuScope3]

The inconsistency for the package related schema has been fixed
release version:

• Version for Python client: 2.19.0
• Version for Typescript client: 3.7.1