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: omitempty targeting field in Flag structure #247

Merged
merged 1 commit into from
Jan 5, 2023

Conversation

skyerus
Copy link
Contributor

@skyerus skyerus commented Jan 5, 2023

This PR

Added omitempty to the json tags of the targeting field in the Flag structure.

Related Issues

Fixes #246

Notes

Follow-up Tasks

How to test

Signed-off-by: Skye Gill <gill.skye95@gmail.com>
@beeme1mr beeme1mr self-requested a review January 5, 2023 17:04
@beeme1mr beeme1mr merged commit 3f406b5 into open-feature:main Jan 5, 2023
beeme1mr pushed a commit that referenced this pull request Jan 6, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.3.0](v0.2.7...v0.3.0)
(2023-01-06)


### ⚠ BREAKING CHANGES

* consolidated configuration change events into one event
([#241](#241))

### Features

* consolidated configuration change events into one event
([#241](#241))
([f9684b8](f9684b8))
* support yaml evaluator
([#206](#206))
([2dbace5](2dbace5))


### Bug Fixes

* changed eventing configuration mutex to rwmutex and added missing lock
([#220](#220))
([5bbef9e](5bbef9e))
* omitempty targeting field in Flag structure
([#247](#247))
([3f406b5](3f406b5))

---
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] Marshalling eval.Flags struct to JSON triggers "invalid JSON file" error
3 participants