feat(creatives): expose per-subtype *CreativeFieldNames on creatives get#417
Merged
Conversation
Add `--cpc-video-creative-field-names`, `--cpm-video-creative-field-names`, `--smart-creative-field-names`, and `--video-extension-creative-field-names` to `direct creatives get` for the four nested WSDL `*FieldNames` request parameters declared by `CreativesGetRequest` (`CpcVideoCreativeFieldEnum`: `Duration`; `CpmVideoCreativeFieldEnum`: `Duration`; `SmartCreativeFieldEnum`: `CreativeGroupId`, `CreativeGroupName`, `BusinessType`; `VideoExtensionCreativeFieldEnum`: `Duration`). Mirrors the Wave 1 sitelinks pattern (#403). Each flag parses CSV via `parse_csv_strings`, rejects empty input with `click.UsageError`, and only injects the WSDL key when non-empty (Yandex falls back to its server-side default otherwise). The four options share one selector loop instead of four near-duplicate blocks. Removes the corresponding rows from `NESTED_FIELDNAMES_EXCLUSIONS` so `test_every_nested_fieldnames_param_has_cli_option` enforces all four flags. Adds parametrized dry-run tests for payload, default-omission, `--help` visibility, and empty-CSV rejection. Closes #411. Co-Authored-By: Claude Opus 4.7 <[email protected]>
Owner
Author
|
@claude review. Focus on critical issues: bugs, security vulnerabilities, logical errors, data loss risks, performance problems. Do NOT nitpick style, naming conventions, minor formatting, or subjective preferences — only flag issues that could break functionality or cause real harm in production. |
|
Claude finished @axisrow's task in 1m 33s —— View job Code ReviewFocused on critical issues per request — no bugs, security holes, logic errors, data-loss risks, or perf concerns found. The implementation is a faithful mirror of the Wave 1 sitelinks pattern in Critical checks (all pass)
Non-critical observations (informational, not blockers)
VerdictNo production-impacting issues. LGTM for merging from a critical-correctness perspective.
|
axisrow
added a commit
that referenced
this pull request
May 28, 2026
axisrow
added a commit
that referenced
this pull request
May 28, 2026
axisrow
added a commit
that referenced
this pull request
May 28, 2026
Resolve conflicts with #415 #416 #417 #418 #419 #420: keep all six previously-merged CHANGELOG entries (feeds/keywords/creatives/clients/ agencyclients/adgroups) and place the campaigns BREAKING CHANGES block at the end of Unreleased. Drop the already-removed NESTED_FIELDNAMES_EXCLUSIONS rows. Update the surviving legacy `-fields` test fixtures to the new `-field-names` form, while keeping one explicit rejection test for `--text-campaign-fields` (the old name).
axisrow
added a commit
that referenced
this pull request
May 28, 2026
Resolve conflicts with #415 #416 #417 #418 #419 #420 #421: keep all six previously-merged CHANGELOG entries (feeds/keywords/creatives/clients/ agencyclients/adgroups), the campaigns BREAKING CHANGES block, and add the bidmodifiers entry as a separate 'Additional features' block. Drop already-removed NESTED_FIELDNAMES_EXCLUSIONS rows. Append bidmodifiers tests after the canonical campaigns block in test_dry_run.py.
This was referenced May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--*-creative-field-namesflags todirect creatives getfor the nested WSDL*FieldNamesrequest parameters declared byCreativesGetRequest:--cpc-video-creative-field-names(CpcVideoCreativeFieldEnum:Duration)--cpm-video-creative-field-names(CpmVideoCreativeFieldEnum:Duration)--smart-creative-field-names(SmartCreativeFieldEnum:CreativeGroupId,CreativeGroupName,BusinessType)--video-extension-creative-field-names(VideoExtensionCreativeFieldEnum:Duration)NESTED_FIELDNAMES_EXCLUSIONSso the regression test enforces all four flags.Closes #411. Third PR in Wave 2 milestone 0.3.14.
Test plan
pytest tests/test_api_coverage.py::test_every_nested_fieldnames_param_has_cli_option— passes after row removal.pytest tests/test_dry_run.py -k creatives_get— 7 tests pass (payload, default-omission, --help, 4 parametrized empty-CSV rejections).pytest tests/test_api_coverage.py tests/test_cli.py tests/test_comprehensive.py— 68 tests pass.direct creatives get --help | grep creative-field-names— 4 flags visible.🤖 Generated with Claude Code