dotnet add package Our.FeatureFlags --version 2.0.0
NuGet\Install-Package Our.FeatureFlags -Version 2.0.0
<PackageReference Include="Our.FeatureFlags" Version="2.0.0" />
paket add Our.FeatureFlags --version 2.0.0
#r "nuget: Our.FeatureFlags, 2.0.0"
// Install Our.FeatureFlags as a Cake Addin #addin nuget:?package=Our.FeatureFlags&version=2.0.0 // Install Our.FeatureFlags as a Cake Tool #tool nuget:?package=Our.FeatureFlags&version=2.0.0
Enables you to use Microsoft.FeatureManagement to not only control your front end by these filters and flags but also your back office properties.
These properties can still be mandatory and have validation.
Follow the install step(s) for Microsoft.FeatureManagement.
The package will register its dependencies using a Composer so no additional configuration is needed.
Create the data type you want to wrap then create a Feature Flagged data type that wraps it. Within your code use the FeatureManager as per the Microsoft.FeatureManagement documentation.
Properties work with Models builder as if there were not feature flagged.
Known Issues and work arounds
Uses the base property value converter method of checking this, as I am unable to get the correct converter on this request.
I would suggest never using HasValue and instead null check etc the strongly type value.
The logo for Our.FeatureFlags - Toggle icons created by Freepik - Flaticon
|Product||Versions Compatible and additional computed target framework versions.|
|.NET||net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed.|
This package is not used by any NuGet packages.
This package is not used by any popular GitHub repositories.