Skip to content

AN-451008 paid-media: add missing title on nested leaf properties#2171

Open
ejsuncy wants to merge 1 commit into
adobe:masterfrom
ejsuncy:AN-451008-issue-2170-paid-media-titles
Open

AN-451008 paid-media: add missing title on nested leaf properties#2171
ejsuncy wants to merge 1 commit into
adobe:masterfrom
ejsuncy:AN-451008-issue-2170-paid-media-titles

Conversation

@ejsuncy
Copy link
Copy Markdown
Contributor

@ejsuncy ejsuncy commented May 14, 2026

Summary

Several nested-object leaf properties in the paid-media fieldgroup
schemas were missing the title keyword (and description in most
cases). Downstream consumers (CJA Workspace, schema editors, docs) were
falling back to the full dot-notation schemaPath as the display name
— surfacing raw paths like
paidMedia.attributionMetrics.crossDeviceAttribution.devicePathBreakdown.mobileToMobileApp
in the UI instead of a human-readable label.

Sibling properties at the same nesting level all have title set, so
this was an oversight in three inline object definitions, not an
intentional pattern.

Affected fields

components/fieldgroups/paid-media/core-paid-media-attribution-metrics.schema.json

  • xdm:devicePathBreakdown leaves: mobileToDesktop, desktopToMobile, mobileToMobileApp
  • xdm:channelSequence.items: channel, position, weight

components/fieldgroups/paid-media/core-paid-media-campaign-details.schema.json

  • xdm:dayParting.schedule.items: dayOfWeek, startHour, endHour

Backwards compatibility

No breaking changes. Only title and description metadata are added;
property names, types, and constraints are unchanged.

npm test and npm run validate components/fieldgroups/paid-media both
pass on this branch.

Issue: #2170
Jira: AN-451008

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

## Summary

Several nested-object leaf properties in the paid-media fieldgroup
schemas were missing the `title` keyword (and `description` in most
cases). Downstream consumers (CJA Workspace, schema editors, docs) were
falling back to the full dot-notation `schemaPath` as the display name
— surfacing raw paths like
`paidMedia.attributionMetrics.crossDeviceAttribution.devicePathBreakdown.mobileToMobileApp`
in the UI instead of a human-readable label.

Sibling properties at the same nesting level all have `title` set, so
this was an oversight in three inline object definitions, not an
intentional pattern.

## Affected fields

`components/fieldgroups/paid-media/core-paid-media-attribution-metrics.schema.json`
  - `xdm:devicePathBreakdown` leaves: `mobileToDesktop`, `desktopToMobile`, `mobileToMobileApp`
  - `xdm:channelSequence.items`: `channel`, `position`, `weight`

`components/fieldgroups/paid-media/core-paid-media-campaign-details.schema.json`
  - `xdm:dayParting.schedule.items`: `dayOfWeek`, `startHour`, `endHour`

## Backwards compatibility

No breaking changes. Only `title` and `description` metadata are added;
property names, types, and constraints are unchanged.

`npm test` and `npm run validate components/fieldgroups/paid-media` both
pass on this branch.

Issue: adobe#2170
Jira: AN-451008

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ejsuncy ejsuncy marked this pull request as ready for review May 14, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant