Current State
generateSettings uses a standard and chart to generate a 'default' settings object (with an option to leave some values undefined vi the partial option). A settings shell object for eDish (representing a default configuration) is saved in the function. This isn't very flexible, generalizable or scalable.
Future State
Create a more generalizable framework, where generateSettings creates a default object using the various metadata files, and then users can provide a customSettings object that overwrites default values (via setSettingValue()).
Details
- Remove the "shell" setting list for eDish currently saved in
generateSettings. We want to generate this algorithmically instead. We might want to start with the code @pburnsdata wrote for the previous more limited refactor
- Need to figure out the best way to store the "default" values for setting other than data mappings.
customSettings should be optional. Not sure if it's best to structure that parameter as a settings object or as an array of key/value pairs ...
Current State
generateSettingsuses astandardandchartto generate a 'default'settingsobject (with an option to leave some values undefined vi thepartialoption). A settings shell object for eDish (representing a default configuration) is saved in the function. This isn't very flexible, generalizable or scalable.Future State
Create a more generalizable framework, where
generateSettingscreates a default object using the various metadata files, and then users can provide acustomSettingsobject that overwrites default values (viasetSettingValue()).Details
generateSettings. We want to generate this algorithmically instead. We might want to start with the code @pburnsdata wrote for the previous more limited refactorcustomSettingsshould be optional. Not sure if it's best to structure that parameter as a settings object or as an array of key/value pairs ...