[Flags] fix: add STATIC resolution reason#3131
Conversation
|
🎯 Code Coverage 🔗 Commit SHA: 96b1913 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feature/flags-ofeat #3131 +/- ##
=======================================================
+ Coverage 70.81% 71.00% +0.19%
=======================================================
Files 899 899
Lines 33137 33145 +8
Branches 5592 5594 +2
=======================================================
+ Hits 23465 23534 +69
+ Misses 8108 8068 -40
+ Partials 1564 1543 -21
🚀 New features to boost your workflow:
|
| enum class ResolutionReason { | ||
| /** | ||
| * The resolved value is the default value for the flag. | ||
| * No targeting rules matched; the fallthrough/default allocation was used. |
There was a problem hiding this comment.
another reason is the "allocation override" that forces a variant value
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
What does this PR do?
This PR adds the STATIC resolution reason to the
flagsandflags-openfeaturemodulesMotivation
This resolution reason is returned from the flagging service when a flag's value is determined by the platform default rather than any targeting rules
Review checklist (to be filled by reviewers)