dglazkov
commented
1 year ago - The
*ConfigStoreclass operates on some store, so it must be given some knowledge about location of the store (file path in JSON, document/collection path in Firestore). This is knowledge is passed as constructor arguments. - Instances of
*ConfigStoreare produced by*ConfigLoader. This class knows all locations of files and paths to instantiate the right*ConfigStore, and has methods for each. There is oneConfigStoreper type of storage. - When writing a Polymath app, developer instantiates a
*ConfigLoaderof the kind that's appropriate for their setup. Everything else within the Polymath library is oblivious to specifics. - Developer can also create their own
*ConfigLoaderinstance. For example, they can introduce a different kind of store, or they can use it to mash existing ones together: one kind of store for directory and another for host, etc.
dalmaer
JSON config files are great for small-scale projects, but a more robust solution is needed for larger scale.
https://github.com/dglazkov/polymath-host uses Firestore, for example. Here's a path to get there, expressed as a set of interlocked patterns:
*Configclasses. Each class takes in a simpledict[str, str]and offers simple accessors with good defaults and type conversion if necessary. For example,HostConfig,InfoConfig, etc.*ConfigStoreclass. The class is not specialized to each kind of config, it's just a way to read the store. It is specialized for the type of storage:JSONConfigStore,FirestoreConfigStore, etc.*Configclass has acreateclass method that takes a*ConfigStoreclass to produce the right instance.(to be continued)