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

chore: prepare for Yggdrasil with deprecations of changing API #237

Merged
merged 3 commits into from
Sep 3, 2024

Conversation

daveleek
Copy link
Collaborator

@daveleek daveleek commented Sep 2, 2024

Deprecations in preparation of Yggdrasil PR that removes some public APIs

@@ -31,6 +31,7 @@ public ToggleBootstrapUrlProvider(string path, HttpClient client, UnleashSetting
this.customHeaders = customHeaders;
}

[Obsolete("Will return json string in the next major version", false)]
Copy link
Member

Choose a reason for hiding this comment

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

Think we should do a different method rather than changing the return type

Copy link
Member

@sighphyre sighphyre left a comment

Choose a reason for hiding this comment

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

Yeah LGTM

@daveleek daveleek merged commit 26e5fc2 into main Sep 3, 2024
2 checks passed
@daveleek daveleek deleted the chore/yggdrasil-prep-deprecations branch September 3, 2024 14:01
@rcollette
Copy link

What is the replacement for .FeatureToggles?

@sighphyre
Copy link
Member

What is the replacement for .FeatureToggles?

There likely won't be a direct replacement. To be completely honest there's still some debate to be had here. The two options (not necessarily competing) are to either return a raw JSON string, which is the unparsed response directly from the server, or a list of names of each of the feature toggles known.

IMO exposing the feature toggles directly was never a very good idea, outside of exposing their names.

I'm open to suggestions if you're using this in some way we hadn't considered yet though

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.

3 participants