Closed 8ma10s closed 4 weeks ago
Name | Link |
---|---|
Latest commit | ce61272685db5d3d60085312bf97855c3c3014e3 |
Latest deploy log | https://app.netlify.com/sites/go-feature-flag-doc-preview/deploys/671a3df485f8e30008413b7a |
Attention: Patch coverage is 94.73684%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 85.48%. Comparing base (
a1955f0
) to head (ce61272
). Report is 1 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
cmd/relayproxy/service/gofeatureflag.go | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Sorry about the repeated commits. I think I've fixed the issue, and hopefully it works now.
Thanks a lot for your contribution @8ma10s this is really great.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
@thomaspoignant Thank you for reviewing and giving me suggestions! 🚀
Description
This pull request introduces a new feature to disable notifications on initialization and refactors the caching mechanism to support this feature. It also includes updates to the test suite to ensure the new functionality works as expected.
Problem
Resolution
DisableNotificationOnInit
configuration key. If set to true, avoid sending the notification on cache initialization (it will still send notification when the change is detected AFTER initialization)How to test
go test ./...
ffClient
should do the trick too.Closes issue(s)
Resolve #2532
Checklist
README.md
and/website/docs
)