direct-cli 0.3.10__tar.gz → 0.3.12__tar.gz

{direct_cli-0.3.10 → direct_cli-0.3.12}/CHANGELOG.md

@@ -1,5 +1,116 @@
 # Changelog
 
+## 0.3.12
+
+**Added:**
+
+- `direct ads update` now exposes `--callouts-add`, `--callouts-remove`,
+  and `--callouts-set` for managing the
+  `TextAdUpdateBase.CalloutSetting` field
+  (`ext:AdExtensionSetting`). Each flag accepts a comma-separated list
+  of `CALLOUT`-type ad-extension IDs; `--callouts-set` replaces the
+  full callout list and is mutually exclusive with the incremental
+  `--callouts-add` / `--callouts-remove` pair (enforced via
+  `click.UsageError` before any request is built). Flags are
+  TEXT_AD-only — per-subtype validation rejects them on `TEXT_IMAGE_AD`
+  / `MOBILE_APP_AD` with the standard "not compatible with --type"
+  message. Empty CSV input is rejected up-front rather than silently
+  producing a no-op payload. Closes #238.
+- `direct adgroups add` and `direct adgroups update` now expose
+  `--tracking-params` for the top-level `AdGroup*.TrackingParams`
+  field. Values are limited to the documented 1024-character maximum;
+  `update` does not require `--type` because the field belongs to the
+  ad group item itself, not a subtype block. Closes #242.
+- `direct adgroups add` and `direct adgroups update` now expose
+  `--negative-keywords` and `--negative-keyword-shared-set-ids` for
+  `NegativeKeywords.Items` and `NegativeKeywordSharedSetIds.Items`.
+  Empty list input is rejected, shared-set IDs are parsed as integers,
+  and `update` treats either flag as a meaningful field for the
+  no-op guard. Closes #243.
+- `direct ads update --type TEXT_AD` now exposes
+  `--video-extension-creative-id` for `TextAd.VideoExtension.CreativeId`
+  and `--price-extension-price`, `--price-extension-old-price`,
+  `--price-extension-price-qualifier`, and
+  `--price-extension-price-currency` for `TextAd.PriceExtension`.
+  These flags are TEXT_AD-only and are rejected on other ad subtypes
+  before any request is built. Closes #245.
+- `direct vcards add` now exposes `--instant-messenger-client` and
+  `--instant-messenger-login` for `InstantMessenger.MessengerClient`
+  and `InstantMessenger.MessengerLogin`, plus the six
+  `--point-on-map-*` coordinate flags for `PointOnMap`. Partial
+  `InstantMessenger` or `PointOnMap` input is rejected with
+  `click.UsageError` so required nested WSDL fields are not omitted.
+  Closes #246.
+- `direct feeds add` and `direct feeds update` now expose
+  `--remove-utm-tags`, `--feed-login`, and `--feed-password` for
+  `UrlFeed.RemoveUtmTags`, `UrlFeed.Login`, and `UrlFeed.Password`.
+  `feeds update` also exposes `--clear-feed-login` and
+  `--clear-feed-password` for the nillable credential fields, with
+  mutual-exclusion checks against the corresponding set flags.
+  `FileFeed` upload/base64 support was split to follow-up #264.
+  Closes #253.
+- `direct retargeting add` and `direct retargeting update` now expose
+  `--description` for the optional retargeting-list `Description`
+  field. Description input is validated against the documented maximum
+  length before building the request, and update-only description
+  changes satisfy the no-op guard. Closes #256.
+- `direct sitelinks add` now supports `TurboPageId` for
+  `SitelinkAddItem.TurboPageId` through the canonical `--sitelink`
+  pipe spec by accepting an optional fourth segment after
+  `Title|Href|Description`. Rows must provide either `Href` or
+  `TurboPageId`, so Turbo-only sitelinks are accepted without relaxing
+  empty-row validation. Closes #257.
+
+**Changed:**
+
+- WSDL parity now includes a soft optional-field audit for issue #239.
+  `scripts/build_wsdl_optional_field_audit.py --check` regenerates and
+  compares `tests/WSDL_OPTIONAL_FIELD_AUDIT.md`, covering cached mutating
+  WSDL item fields at unbounded nesting depth. Confirmed `minOccurs=0`
+  gaps are tracked as linked `missing_followup` rows instead of being
+  invisible to the required-field gate.
+
+## 0.3.11
+
+**Added:**
+
+- `direct campaigns add` and `direct campaigns update` now expose
+  `--tracking-params` for the campaign-level tracking query string
+  (`TextCampaign` / `DynamicTextCampaign` / `SmartCampaign` `.TrackingParams`).
+  `campaigns update` gained an optional `--type` discriminator —
+  required when `--tracking-params` is set, validated against
+  the three subtypes supported by the CLI. Backward compatible:
+  existing `campaigns update --id N --name X` calls without `--type`
+  keep working unchanged. Closes #230.
+- `direct v4account account-management` now supports `--action Get`,
+  `Deposit`, `Invoice`, and `TransferMoney` in addition to `Update`,
+  matching the official v4 Live docs
+  (<https://yandex.ru/dev/direct/doc/dg-v4/reference/AccountManagement-docpage/>).
+  `Get` is read-only and accepts optional `--logins` / `--account-ids`
+  filters. `Deposit`, `Invoice`, and `TransferMoney` are financial
+  mutations: they need `--finance-token` (or `--master-token` +
+  `--operation-num` + `--finance-login`) and respect the existing
+  dry-run-unless-sandbox rule. A Click-side allow-list rejects flags
+  that do not belong to the chosen action before any body is built.
+  Refs #125.
+
+**Fixed:**
+
+- `direct v4 *` command wrappers now let `click.ClickException`
+  (including `UsageError` from `call_v4` shape validation) propagate to
+  Click instead of swallowing it in the generic `except Exception`.
+  Shape-validation errors keep their usage hint and exit with code 2,
+  matching Click's contract; non-Click runtime errors still surface
+  through `print_error` + `Abort` (exit 1). Closes #227.
+
+**Breaking changes:**
+
+- `direct v4finance get-credit-limits` no longer accepts `--logins`; the
+  request body now omits `param` per the official v4 Live docs
+  (<https://yandex.ru/dev/direct/doc/dg-v4/reference/GetCreditLimits.html>),
+  which define the body as `method`, `finance_token`, and `operation_num`
+  only. Refs #125.
+
 ## 0.3.10
 
 **Added:**

{direct_cli-0.3.10 → direct_cli-0.3.12}/CLAUDE.md

@@ -52,12 +52,13 @@ Click group-of-groups. Each Yandex Direct API resource = one file in `direct_cli
 
 A guard in `tests/test_api_coverage.py::test_dry_run_exclusions_have_no_helper_or_legacy_rationale` enforces this — any rationale outside those five categories that uses the banned phrasing is a mis-classification: write a `PAYLOAD_CASES` fixture instead. See post-mortem in issue #199.
 
-**WSDL parity gate:** `tests/test_wsdl_parity_gate.py` runs four invariant checks across every `add`/`update`/`set` command in `WRITE_SANDBOX`:
+**WSDL parity gate:** `tests/test_wsdl_parity_gate.py` runs four hard invariant checks across every `add`/`update`/`set` command in `WRITE_SANDBOX`, plus one soft optional-field audit:
 
 1. *Empty subtype no-op* — a mutating command with only the resource ID must refuse to send the payload (no silent no-op on the live API).
 2. *Silent data loss* — a typed flag that does not belong to the chosen `--type` must raise `UsageError`, not be dropped.
 3. *WSDL `minOccurs=1` not validated* — every required WSDL item field must be enforced either via Click `required=True` *or* a documented `UsageError` body check (listed in `INTERNAL_VALIDATION`).
 4. *Strategy enum drift* — `STRATEGY_TYPES` (`direct_cli/commands/strategies.py`) must equal the subtype-of-one field names in `StrategyAddItem`.
+5. *Optional-field visibility* — `scripts/build_wsdl_optional_field_audit.py --check` compares cached WSDL item fields (including `minOccurs=0`, at unbounded nesting depth) with `tests/WSDL_OPTIONAL_FIELD_AUDIT.md`. Confirmed misses stay soft-gated as `missing_followup` rows linked to GitHub issues; they do not fail CI as missing CLI flags until implemented.
 
 Adding a new mutating command requires extending `COMMAND_WSDL_MAP` in `tests/test_wsdl_parity_gate.py` (the coverage test fails otherwise) and, if the WSDL request has a non-mechanical field name, also `WSDL_FIELD_TO_CLI_OPTION`. Tracked in issue #198.