adobe / adobe/xdm

Schema naming does not follow a consistent convention

Open
#512 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
266
Forks
380
Avg merge
5d 8h
Merged PRs (30d)
9

Description

## What are the schemas that are affected by the issue
`person-name`, `beacon-interaction-details`, `advertising-break`, `direct-marketing`, ...

## What are examples of products that are impacted by the issue
Any product that uses these schemas.

We seem to have two approaches to schema naming:
* concatenate the words without spaces, convert to all lowercase
* separate the names with hyphens, convert to all lowercase

Why are we using different naming conventions? What is the best practice?

Contributor guide

Open the contributing guide

Research direction

Review the affected schema names, including `person-name`, `beacon-interaction-details`, `advertising-break`, and `direct-marketing`, and compare the two naming approaches described in the issue. Determine which convention should apply to schemas and identify the complete set of impacted products or schemas. The issue does not name files or tests, so the scope and completion criteria need clarification before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
data
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.