When a new contributor starts mapping for a codebase, he opens the map using StrongDMM and does the changes, then files a PR for it to be merged.
The issue is, there is no way to ensure the settings he has are consistent, eg. in our codebase we require that all vars are sanitized, all maps are in TGM, and nudge is done with pixel_x/y, but we have no way to enforce that, we can just hope the contributor will read the readme and configure those settings
Sugest a solution
When an environment is loaded (.DME) alongside a map, look in the same directory of the .DME for a file whose settings will be used instead of preferences.json inside said environment
Only the settings specified in said file are overriding the preferences in preferences.json
Problem to be solved
When a new contributor starts mapping for a codebase, he opens the map using StrongDMM and does the changes, then files a PR for it to be merged.
The issue is, there is no way to ensure the settings he has are consistent, eg. in our codebase we require that all vars are sanitized, all maps are in TGM, and nudge is done with pixel_x/y, but we have no way to enforce that, we can just hope the contributor will read the readme and configure those settings
Sugest a solution
When an environment is loaded (.DME) alongside a map, look in the same directory of the .DME for a file whose settings will be used instead of
preferences.jsoninside said environmentOnly the settings specified in said file are overriding the preferences in
preferences.json