-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: erroneous warning about prop overwrite #924
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Craig Pastro <pastro.craig@gmail.com>
✅ Deploy Preview for polite-licorice-3db33c canceled.
|
craigpastro
changed the title
bug: create new context when adding flagd properties
fix: create new context when adding flagd properties
Sep 19, 2023
Codecov Report
@@ Coverage Diff @@
## main #924 +/- ##
==========================================
- Coverage 72.71% 72.62% -0.09%
==========================================
Files 28 28
Lines 2855 2857 +2
==========================================
- Hits 2076 2075 -1
- Misses 683 685 +2
- Partials 96 97 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
beeme1mr
approved these changes
Sep 19, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks! 😃
toddbaert
approved these changes
Sep 19, 2023
LGTM! |
toddbaert
changed the title
fix: create new context when adding flagd properties
fix: erroneous warning about prop overwrite
Sep 19, 2023
Merged
toddbaert
pushed a commit
that referenced
this pull request
Oct 12, 2023
🤖 I have created a release *beep* *boop* --- <details><summary>flagd: 0.6.7</summary> ## [0.6.7](flagd/v0.6.6...flagd/v0.6.7) (2023-10-12) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.6.6 ([#916](#916)) ([1f80e4d](1f80e4d)) * **deps:** update module github.com/open-feature/go-sdk-contrib/providers/flagd to v0.1.17 ([#759](#759)) ([a2a2c3c](a2a2c3c)) * **deps:** update module github.com/spf13/viper to v1.17.0 ([#956](#956)) ([31d015d](31d015d)) * **deps:** update module go.uber.org/zap to v1.26.0 ([#917](#917)) ([e57e206](e57e206)) ### 🧹 Chore * docs rework ([#927](#927)) ([27b3193](27b3193)) ### 📚 Documentation * fixed typos and linting issues ([#957](#957)) ([0bade57](0bade57)) </details> <details><summary>flagd-proxy: 0.2.12</summary> ## [0.2.12](flagd-proxy/v0.2.11...flagd-proxy/v0.2.12) (2023-10-12) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.6.6 ([#916](#916)) ([1f80e4d](1f80e4d)) * **deps:** update module github.com/spf13/viper to v1.17.0 ([#956](#956)) ([31d015d](31d015d)) * **deps:** update module go.uber.org/zap to v1.26.0 ([#917](#917)) ([e57e206](e57e206)) </details> <details><summary>core: 0.6.7</summary> ## [0.6.7](core/v0.6.6...core/v0.6.7) (2023-10-12) ### 🐛 Bug Fixes * **deps:** update module github.com/prometheus/client_golang to v1.17.0 ([#939](#939)) ([9065cba](9065cba)) * **deps:** update module github.com/rs/cors to v1.10.1 ([#946](#946)) ([1c39862](1c39862)) * **deps:** update module go.uber.org/zap to v1.26.0 ([#917](#917)) ([e57e206](e57e206)) * **deps:** update module golang.org/x/mod to v0.13.0 ([#952](#952)) ([be61450](be61450)) * **deps:** update module golang.org/x/sync to v0.4.0 ([#949](#949)) ([faa24a6](faa24a6)) * **deps:** update module google.golang.org/grpc to v1.58.1 ([#915](#915)) ([06d95de](06d95de)) * **deps:** update module google.golang.org/grpc to v1.58.2 ([#928](#928)) ([90f1878](90f1878)) * **deps:** update module google.golang.org/grpc to v1.58.3 ([#960](#960)) ([fee1558](fee1558)) * **deps:** update opentelemetry-go monorepo ([#943](#943)) ([e7cee41](e7cee41)) * erroneous warning about prop overwrite ([#924](#924)) ([673b76a](673b76a)) ### ✨ New Features * add `$flagd.timestamp` to json evaluator ([#958](#958)) ([a1b04e7](a1b04e7)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
When adding flagdProperties to the context in preparation for evaluation return a new context so that it doesn't affect any references to the current context.
Without this change:
With this change:
Both logs were triggered by the request in the bug report:
Related Issues
Fixes #923.
Notes
Follow-up Tasks
How to test