Skip to content
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.

Support local and global configuration and merge them appropriately #14

Open
MythicManiac opened this issue Dec 22, 2020 · 0 comments
Open

Comments

@MythicManiac
Copy link
Member

It would be a good idea to support a global configuration for defaults, and allow for specifying project-specific local configuration overrides.

A simple example could be that you have globally configured the cyberpunk2077 game to point to one path, but want to use a different path for a specific project e.g. to an older version of the game.

So the spec is fairly simple:

  1. There should be a global configuration file where defaults can be configured to
  2. Each project should have a local configuration file where overrides to the globals can be stored to. This could be stored in the .gpm directory for example
  3. When loading a configuration, gpm would first load the global configuration, then check if a local configuration exists, and finally merge the local configuration on top of the global configuration.

Hard to say which is the best merge strategy at this point yet, left for later discussion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant