Change numeric fields to be of type integer
- 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
* schemas/context/advertising-break.schema.json
* schemas/context/advertising-timed-asset-reference.schema.json
* schemas/context/advertising-timed-asset-view-details.schema.json
* schemas/context/advertising.schema.json
* schemas/context/media-timed-asset-reference.schema.json
* schemas/context/media-timed-asset-view-details.schema.json
* schemas/context/media-timed-chapter-asset-reference.schema.json
* schemas/context/media-timed-chapter-view-details.schema.json
* schemas/context/media-timed-chapter.schema.json
* schemas/context/media-timed-qoe.schema.json
* schemas/context/media-timed.schema.json
## What are examples of products that are impacted by the issue
* Adobe Media Analytics
Internal JIRA issue: https://jira.corp.adobe.com/browse/VA-3330
High-level changes:
* change the type of some fields from number to integer (only integer values are valid)
* changed the title of some fields to ensure it is aligned with the field name in the reports
Contributor guide
Research direction
Review the eleven schemas listed under schemas/context/, starting with advertising-break.schema.json and the related media-timed schemas. Identify the numeric fields whose types and titles need alignment, then confirm that each affected schema uses integer values and matching field names and titles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100