Documentation for auto-refreshing of features approach

[ScottMathieson]

Hi,

I really appreciate the work carried out to build the SDK for netcore apps but wondered if there is a better approach for using the SDK from netcore that would support automatically refreshing the status of features. The current documentation has the SDK initialised once but does not mention how to manage automatic refreshing of features so that changes can be picked up dynamically without re-starting the application. My current approach is to initialise the context with the API Key and Url for our stand-alone GrowthBook instance and the call loadFeatures() and await it's completion. This happens at service startup and GrowthBook registered as a singleton. I then make a call to loadFeatures() before each access (with force refresh and await completion set to false), relying on the cache-control headers and eTag to prevent overloading the GrowthBook endpoints and accepting it could be a stale value I am picking up. Is there a better way of achieving this - if so could you provide some guidance in the documentation.

Thanks