Feature Flags explicitly excluded?

[earloc]

Hi.

Is there a particular reason why feature-flags are explicitly excluded?

Trying to get hands on integrating with feature-flags and now stumbling over this.

Probably will end up using @azure/app-configuration, yet still wondering why we are not able to maybe at least opt-in to include feature-flags as well

[earloc]

just saw #55. Any ETA for when we can expect FeatureManagement (FM) support?

[Eskibear]

Trying to get hands on integrating with feature-flags and now stumbling over this

Yes, that's the trade-off. But we don't want to create future breaking changes if possible, as described in #55

Repo for feature management: https://github.com/microsoft/FeatureManagement-JavaScript
We will release a preview version soon. For the moment, probably you can checkout the repo and build the tgz package locally and give it a try. Please let us know the early feedback!

[earloc]

yeah, thx for coming back on this. Might try that out, once it got released. In the mean-time, we will probably just stick to @azure/app-configuration, as we currently just want enabled/disabled for the time being, until we need more sophisticated approaches utilizing target-filters.