jejacks0n / jejacks0n/activeexperiment
There should be a complex example of a service based rollout and subscriber
Open
@jejacks0n is already working on this.
Since Dec 11, 2022.
documentation
enhancement
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 0
- Avg merge
- 13h 44m
- Merged PRs (30d)
- 7
Description
The general idea is to provide an example for others to use when writing their own gems if they want to. I think using Unleash for this would make the most sense, but using something like LaunchDarkly might also be useful.
Things that should be built in to the subscriber:
- Metrics on as much as possible -- variant resolution, callback times, etc.
- Include details to understand the variant resolution lifecycle.
- Assigned manually before run?
- Set manually in the run block?
- Set in a run callback? (before and around)
- Resolved through the cache?
- Resolved through segment rules?
- Resolved through the rollout?
- Was the variant cached?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.