We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just want to call out here, In .NET, we have an option to decide the behavior when filter can not be found: https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement/FeatureManagementOptions.cs The default behavior is throwing exception instead of slient error.
And there was a discussion about this design: microsoft/FeatureManagement-Dotnet#248
But it's not necessary to make JS FM lib completely same as .NET FM lib. Just put it here, for your reference.
Originally posted by @zhiyuanliang-ms in #1 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Just want to call out here, In .NET, we have an option to decide the behavior when filter can not be found:
https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement/FeatureManagementOptions.cs
The default behavior is throwing exception instead of slient error.
And there was a discussion about this design: microsoft/FeatureManagement-Dotnet#248
But it's not necessary to make JS FM lib completely same as .NET FM lib. Just put it here, for your reference.
Originally posted by @zhiyuanliang-ms in #1 (comment)
The text was updated successfully, but these errors were encountered: