[Experiment]: Explore using pinia for policy editor
Experiment Summary
- Explore using pinia a single data source between yaml mode and rule mode
- Can potentially be more consistent for both modes and remove a lot of prop drilling
Design
- Try implementation fro smaller part with bypass options for Merge request approval policy
Control vs Candidate Experience
Rollout strategy
- Use feature flag only required on frontend
Target Population
Tracking Details
-
json schema used in
gitlab-experiment tracking.
- Due to data tooling limitations, we should only utilize category, action and label. i.e. try to keep from using property and value. Be aware if adding the experiment context to existing events that use property or value that some concessions will need to be made in order for it to show up in the experiment dashboard.
| sequence |
activity |
category |
action |
label |
|
|
|
|
|