You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For dynamic refresh, user can register some keyvalues as watchedSettings. The provider will monitor whether the watchedSettings are changed, if so, the provider will refresh all keyvalue it loaded. But the JS provider will only include keyvalues which selected by selector. The watchedSettings will not be included in the configuration provided by the provider.
This behavior is inconsistent with .NET provider. The screenshot below shows the .NET provider's behavior.
The text was updated successfully, but these errors were encountered:
It's by design. IMO the sentinel should not be included into configuration if it's not covered by any selector. I remember it has been discussed in the design review.
/cc @zhenlan to confirm that.
I understand this behavior is different from .NET, but I also remember this has been discussed in a design review. I don't remember the exact reason. Is it consistent with our providers for python and k8s?
For dynamic refresh, user can register some keyvalues as watchedSettings. The provider will monitor whether the watchedSettings are changed, if so, the provider will refresh all keyvalue it loaded. But the JS provider will only include keyvalues which selected by selector. The watchedSettings will not be included in the configuration provided by the provider.
This behavior is inconsistent with .NET provider. The screenshot below shows the .NET provider's behavior.
The text was updated successfully, but these errors were encountered: