Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add options specifying behavior when filter is missing.

Open
#3 1 comment 0 reactions 1 assignee View on GitHub

@zhiyuanliang-ms is already working on this.

Since Mar 6, 2025.

Assessment

This issue has not been assessed yet.

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

Dominant language
TypeScript
Stars
19
Forks
6
Avg merge
2d 3h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/FeatureManagement-JavaScript

All issues in microsoft/FeatureManagement-JavaScript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.