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

feat: resolve-all functionality #62

Merged
merged 3 commits into from
Dec 20, 2022
Merged

feat: resolve-all functionality #62

merged 3 commits into from
Dec 20, 2022

Conversation

toddbaert
Copy link
Member

@toddbaert toddbaert commented Dec 18, 2022

Closes: #63

@toddbaert toddbaert marked this pull request as draft December 18, 2022 15:06
Signed-off-by: Todd Baert <toddbaert@gmail.com>
Comment on lines 37 to 43
oneof value {
bool boolValue = 3;
string stringValue = 4;
int64 intValue = 5;
double doubleValue = 6;
google.protobuf.Struct objectValue = 7;
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think oneof is a good solution here. In many languages it generates some convenience functions so we can easily check what value is set.

@toddbaert toddbaert marked this pull request as ready for review December 18, 2022 16:36

// The response value of the boolean flag evaluation, will be unset in the case of error.
oneof value {
bool boolValue = 3;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

linting errors here as boolValue should instead be lower snake cased bool_value, same with the other names

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, resolved.

Signed-off-by: Todd Baert <toddbaert@gmail.com>
@toddbaert toddbaert changed the title feat: resolve all functionality feat: resolve-all functionality Dec 19, 2022
@james-milligan
Copy link
Collaborator

Looks good to me - but going to hold off on approving until I play around with what a map of anyFlag is going to look like in go

@toddbaert
Copy link
Member Author

Looks good to me - but going to hold off on approving until I play around with what a map of anyFlag is going to look like in go

💯 , yep, that was my only mild concern too. I thought it seemed like a nice implementation but it'd be good to have that validated. Thanks!

Signed-off-by: Todd Baert <toddbaert@gmail.com>
@james-milligan
Copy link
Collaborator

LGTM :)

@toddbaert toddbaert merged commit 9ca9ee3 into main Dec 20, 2022
james-milligan pushed a commit that referenced this pull request Dec 20, 2022
🤖 I have created a release *beep* *boop*
---


##
[0.2.6](v0.2.5...v0.2.6)
(2022-12-20)


### Features

* resolve-all functionality
([#62](#62))
([9ca9ee3](9ca9ee3))

---
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>
@github-actions github-actions bot mentioned this pull request Jan 26, 2023
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.

[FEATURE] bulk evaluation
2 participants