Skip to content

Conversation

@hairyhenderson
Copy link
Contributor

This PR

  • adds new client methods Boolean, String, Float, Int, and Object that enable simpler usage (no error handling required)

Related Issues

Fixes #262

Notes

There seems to be a soft consensus on #262, so this may need to change if the TC deems necessary, but I'm submitting this early for discussion's sake.

Follow-up Tasks

How to test

See additional examples provided.

Signed-off-by: Dave Henderson <dhenderson@gmail.com>
Copy link
Contributor

@Kavindu-Dodan Kavindu-Dodan left a comment

Choose a reason for hiding this comment

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

Approving as I think this adds good syntatic sugar to our client API.

But please consider opinion of our TC (cc - @toddbaert @thomaspoignant @lukas-reining )

Copy link
Member

@lukas-reining lukas-reining left a comment

Choose a reason for hiding this comment

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

As discussed, I am in of also having an "errorless" API, as we have it in most other SDKs.
The implementation looks good to me.

Copy link
Member

@thomaspoignant thomaspoignant left a comment

Choose a reason for hiding this comment

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

Sounds good to me, it will simplify the usage of the SDK 🙌

@thomaspoignant thomaspoignant merged commit 7b610c7 into open-feature:main Apr 9, 2024
@hairyhenderson hairyhenderson deleted the hairyhenderson/simplified-eval-methods-262 branch April 9, 2024 17:06
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] Awkward usage when trying to evaluate a boolean flag in a complex conditional

4 participants