v8.0.0

What's Changed

BREAKING CHANGES

• fix!: Remove deprecated methods and constructors. Throw error if using local eval without server-side key by @​rolodato in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/147

Full Changelog: Flagsmith/flagsmith-dotnet-client@v7.1.1...v8.0.0

v7.1.1

What's Changed

• fix: RequestTimeout would return the seconds component of its TimeSpan instead of the total duration in seconds by @​rolodato in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/149

Full Changelog: Flagsmith/flagsmith-dotnet-client@v7.1.0...v7.1.1

v7.1.0

What's Changed

Deprecated FlagsmithClient constructors with more than one parameter

The preferred way to instantiate a FlagsmithClient is now to use the FlagsmithClient(FlagsmithConfiguration) constructor. All other constructors are deprecated.

For example, if you were previously initialising the client like this:

new FlagsmithClient(environmentKey: "my-key", enableAnalytics: true);

You should pass the equivalent FlagsmithConfiguration object instead:

new FlagsmithClient(new FlagsmithConfiguration
{
    EnvironmentKey = "my-key",
    EnableAnalytics = true
});

This gives us more flexibility as SDK authors to add or change configuration options without requiring further breaking changes. It also allows us to provide better inline documentation for each configuration parameter.

Deprecated ApiUrl, EnableClientSideEvaluation, and EnvironmentRefreshIntervalSeconds options

Instead, use ApiUri, EnableLocalEvaluation, and EnvironmentRefreshInterval respectively. This change makes this SDK more consistent with Flagsmith documentation and other SDKs, and improves type safety by accepting Uri and TimeSpan objects instead of deriving them from raw strings or numbers.

Deprecated PollingManager(Func<Task>, int) constructor

Instead, use new PollingManager(callback, TimeSpan.FromSeconds(intervalSeconds)). Almost no users will be affected by this change, as PollingManager is meant for internal use.

v7.0.1

What's Changed

• ci: fix testing workflow by @​matthewelwell in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/132
• fix: missing semver dependency by @​matthewelwell in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/130
• ci: fix release workflow by @​matthewelwell in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/133
• chore: bump version 7.0.1 by @​matthewelwell in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/134

Full Changelog: Flagsmith/flagsmith-dotnet-client@v7.0.0...v7.0.1

v7.0.0

What's Changed

• fix!: Remove flag ID properties/methods by @​rolodato in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/129

Breaking Changes

Version 7 removes the Id methods from the IFlag interface and Flag class to avoid deserialisation problems if this ID is null. A flag's internal ID is an implementation detail that should not be relevant to SDK users. If you have a use case that requires using a flag's internal ID, please create an issue here: https://github.com/Flagsmith/flagsmith-dotnet-client/issues

Full Changelog: Flagsmith/flagsmith-dotnet-client@v6.0.0...v7.0.0

v6.0.0

What's Changed

• Fixes by @​mjwills-k in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/126

Breaking Changes

The changes in this release affect the encoding of identifiers. This is technically fixing an issue where an identifier such as "abc&def" would actually retrieve the flags for the identity "abc" and discard the "&def" portion. Since this change will affect the behaviour for these identities, we are marking it as a major version release.

New Contributors

• @​mjwills-k made their first contribution in https://github.com/Flagsmith/flagsmith-dotnet-client/pull/126

Full Changelog: Flagsmith/flagsmith-dotnet-client@v5.4.3...v6.0.0