Add Consent Policy V2 Mixin
- 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
This is a new mixin intended to be added for profile union schemas. The motivation to add this new mixin is to allow producers of consent information for a merge profile to augment more properties like, exit-time from a consent policy, current status of a profile with respect to a particular consent policy, identity level status and qualification times.
## What are examples of products that are impacted by the issue
Contributor guide
Research direction
No file, test, or implementation entry point is named. Start by locating the profile union schemas and reviewing existing consent-policy mixins, then define the affected schema structure for exit time, current policy status, identity-level status, and qualification times; done means the new Consent Policy V2 mixin is available for those schemas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100