Skip to content
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: add custom marshalling options #1117

Merged

Conversation

beeme1mr
Copy link
Member

@beeme1mr beeme1mr commented Jan 3, 2024

This PR

  • add custom marshalling options

Related Issues

Fixes #1116

Notes

I manually tested to confirm the fix is working. However, it's currently not automatically tested because the issue only affects HTTP-based requests, and the E2E tests use gRPC. I'll create a follow-up task to expand the E2E test suite to include HTTP tests.

@beeme1mr beeme1mr requested a review from a team as a code owner January 3, 2024 16:17
@beeme1mr beeme1mr linked an issue Jan 3, 2024 that may be closed by this pull request
Copy link

netlify bot commented Jan 3, 2024

Deploy Preview for polite-licorice-3db33c canceled.

Name Link
🔨 Latest commit 41c5764
🔍 Latest deploy log https://app.netlify.com/sites/polite-licorice-3db33c/deploys/6596c83e9cfb9000089f4fc2

Copy link

codecov bot commented Jan 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d179a1b) 73.43% compared to head (41c5764) 73.43%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1117   +/-   ##
=======================================
  Coverage   73.43%   73.43%           
=======================================
  Files          32       32           
  Lines        3113     3113           
=======================================
  Hits         2286     2286           
  Misses        719      719           
  Partials      108      108           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@Kavindu-Dodan Kavindu-Dodan force-pushed the 1116-bug-there-is-no-value-key-in-the-evaluation-response branch from 1792d80 to 41c5764 Compare January 4, 2024 15:01
@beeme1mr beeme1mr merged commit e8e49de into main Jan 4, 2024
15 checks passed
@github-actions github-actions bot mentioned this pull request Jan 4, 2024
beeme1mr pushed a commit that referenced this pull request Jan 4, 2024
🤖 I have created a release *beep* *boop*
---


<details><summary>flagd: 0.8.1</summary>

##
[0.8.1](flagd/v0.8.0...flagd/v0.8.1)
(2024-01-04)


### 🐛 Bug Fixes

* **deps:** update module github.com/open-feature/flagd/core to v0.7.3
([#1104](#1104))
([b6c00c7](b6c00c7))
* **deps:** update module github.com/spf13/viper to v1.18.2
([#1069](#1069))
([f0d6206](f0d6206))
</details>

<details><summary>flagd-proxy: 0.4.1</summary>

##
[0.4.1](flagd-proxy/v0.4.0...flagd-proxy/v0.4.1)
(2024-01-04)


### 🐛 Bug Fixes

* **deps:** update module github.com/open-feature/flagd/core to v0.7.3
([#1104](#1104))
([b6c00c7](b6c00c7))
* **deps:** update module github.com/spf13/viper to v1.18.2
([#1069](#1069))
([f0d6206](f0d6206))
</details>

<details><summary>core: 0.7.4</summary>

##
[0.7.4](core/v0.7.3...core/v0.7.4)
(2024-01-04)


### 🐛 Bug Fixes

* add custom marshalling options
([#1117](#1117))
([e8e49de](e8e49de))
* **deps:** update kubernetes packages to v0.29.0
([#1082](#1082))
([751a79a](751a79a))
* **deps:** update module connectrpc.com/connect to v1.14.0
([#1108](#1108))
([0a41aca](0a41aca))
* **deps:** update module github.com/prometheus/client_golang to v1.18.0
([#1110](#1110))
([745bbb0](745bbb0))
* **deps:** update module golang.org/x/crypto to v0.17.0 [security]
([#1090](#1090))
([26681de](26681de))
* **deps:** update module google.golang.org/protobuf to v1.32.0
([#1106](#1106))
([e0d3b34](e0d3b34))
</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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] There is no "value" key in the evaluation response
4 participants