FeatureToggleProvider does not work with RxJS about ngx-feature-toggle

[willmendesneto]

Hello @humbertosales . Thanks for open this issue.

Looks like, based on your example, the issue is related to your component structure.

If you look at the examples on README.md and on feature-toggle-provider.component.spec.ts tests feature-toggle-provider should wrap feature-toggle component.

<feature-toggle-provider [featureToggleService]="featureService.getAllFeatures()">
  <feature-toggle [featureName]="'categoria'">
    <button type="button" class="btn btn-danger btn-sm" (click)="excluirCategoria(categoria)">
      <i class="fa fa-remove"></i>
    </button>
  </feature-toggle>
</feature-toggle-provider>

Can you check if this behavior still persists using the latest version of ngx-feature-toggle and try to simulate this issue, please? In case of it's still an issue, can you share a link with an example using the stackblitz demo?

[willmendesneto]

Closing this issue by lack of reply

[robert-king]

i think he's trying to say that the feature flags aren't reactive variables, i.e. you can't update the flags during runtime using http requests because feature-toggle-provider [featureToggleService] does not accept an observable or promise. One option is to use a resolver on any component that needs flags, another option is to provide default flags while loading the flags, neither option is great IMO.