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
Clearly, continually creating and destroying the local configs could be avoided, if the generated configs were cached. If the same frozen object is passed again, one could reuse the previous local config.
I can do that if you are interested.
The text was updated successfully, but these errors were encountered:
I am very interested in a feature of namespacing configs. we have different business hours and holidays between our customer service department and our production department, and namespaced business time configs would fix that problem.
@AdnanTheExcellent it is already possible using exactly the syntax I wrote above. Still I would like to address the garbage issue, when one has to switch often (or by user) between different configs.
Often, the local config is used in several parts of an application. For example:
Clearly, continually creating and destroying the local configs could be avoided, if the generated configs were cached. If the same frozen object is passed again, one could reuse the previous local config.
I can do that if you are interested.
The text was updated successfully, but these errors were encountered: