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
Since the development process often starts by using static JSON files before migrating to other forms of storage, it would be useful if this were implemented as a strategy pattern, with the ability for the developer to switch back and forth between implementations. Something like:
Hi, thanks for the suggestion. Could you provide a more detailed description of the strategy pattern, or perhaps link to some relevant literature that you think speaks to how it could be applied here?
In a nutshell, I want to be able to easily switch between different storage strategies. For example, suppose I have a configuration called "dev" that lets me use local JSON files for early development work. Once I'm satisfied with that, I might switch to "stage" mode, where I use a firebase database. What the modes are called should be completely configurable, and there should be some way of a doing a global switch from one mode to the other. Perhaps there might be some global application parameters for this.
Since the development process often starts by using static JSON files before migrating to other forms of storage, it would be useful if this were implemented as a strategy pattern, with the ability for the developer to switch back and forth between implementations. Something like:
The config file would let you have different named configurations.
The text was updated successfully, but these errors were encountered: