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

GrowthBook Types system #160

Merged
merged 17 commits into from
Jan 24, 2025
Merged

Conversation

vazarkevych
Copy link
Collaborator

@vazarkevych vazarkevych commented Dec 16, 2024

GrowthBook Console proposes Boolean, String, Number and JSON types for features:
image

In this PR getting specified feature type instead of JsonElement was implemented:
image

@micheledezanet
Copy link

I like this solution way better than the recent JsonElement change.

@Bohdan-Kim Bohdan-Kim changed the title WIP GrowthBook Types system Dec 27, 2024
@Bohdan-Kim Bohdan-Kim requested a review from Auz January 3, 2025 16:33

/**
* Feature Evaluator Class
* Takes Context and Feature Key
* Returns Calculated Feature Result against that key
*/
internal class GBFeatureEvaluator {
internal class GBFeatureEvaluator(
private val context: GBContext,

Choose a reason for hiding this comment

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

Let us not tie in FeatureEvaluator to context. We're moving away from this approach.

We'd want the Growthbook instance be decoupled from the context, use an evaluation context for feature eval operations. See the recent changes made to support multi-context in java sdk for more details.

@Bohdan-Kim Bohdan-Kim removed the request for review from Auz January 9, 2025 07:31
@august-growthbook
Copy link

I'm not able to review this, but @madhuchavva or @bryce-fitzsimons are probably the best people to do so.

@Bohdan-Kim Bohdan-Kim merged commit ec754bd into main Jan 24, 2025
2 checks passed
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.

5 participants