feat: allow blank targeting keys#2981
Conversation
Co-authored-by: Nikita Ogorodnikov <[email protected]>
|
/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
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feature/feature-flagging #2981 +/- ##
============================================================
+ Coverage 71.16% 71.24% +0.08%
============================================================
Files 859 859
Lines 31320 31320
Branches 5283 5282 -1
============================================================
+ Hits 22287 22311 +24
+ Misses 7542 7537 -5
+ Partials 1491 1472 -19
🚀 New features to boost your workflow:
|
|
🎯 Code Coverage 🔗 Commit SHA: fa30ccd | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
What does this PR do?
Remove restriction on blank/whitespace-only targeting keys
Motivation
A blank targeting key is valid and supported.
Additional Notes
While a blank targeting key is discouraged, it does not present technical problems. Customers are coached on proper use of targeting key
Review checklist (to be filled by reviewers)