microsoft / microsoft/FeatureManagement-JavaScript
Add options specifying behavior when filter is missing.
@zhiyuanliang-ms is already working on this.
Since Mar 6, 2025.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 6
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 4
Description
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: https://github.com/microsoft/FeatureManagement-Dotnet/issues/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 https://github.com/microsoft/FeatureManagement-JavaScript/pull/1#discussion_r1514055834
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.