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
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Per the modular skeleton discussion, we need to likely allow providing arrays to the ConfigAggregator constructor. This could be done in one of two ways:
an ArrayProvider, which would accept an array to the constructor, and then simply return it on invocation.
an actual array
The former would work with the current architecture, and only require an additional class.
The latter approach would likely require changing loadConfigFromProviders() to work differently, as it presently assumes a provider is a callable.
The text was updated successfully, but these errors were encountered:
Per the modular skeleton discussion, we need to likely allow providing arrays to the
ConfigAggregator
constructor. This could be done in one of two ways:ArrayProvider
, which would accept an array to the constructor, and then simply return it on invocation.The former would work with the current architecture, and only require an additional class.
The latter approach would likely require changing
loadConfigFromProviders()
to work differently, as it presently assumes a provider is a callable.The text was updated successfully, but these errors were encountered: