The json example for consentpolicyResultsMap has a bad field name
Open
- 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
components/fieldgroups/profile/profile-consentResultsv2.example.1.json#L21
`ts` should be instead of `timestamp`
## What are examples of products that are impacted by the issue
RTCDP
Contributor guide
Research direction
Open components/fieldgroups/profile/profile-consentResultsv2.example.1.json at line 21 and inspect the consentpolicyResultsMap example. Confirm the field is currently named timestamp, change it to ts, and verify that the example now uses the requested field name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100