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
{{ message }}
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.
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:
There should be a global configuration file where defaults can be configured to
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
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
.gpm
directory for exampleHard to say which is the best merge strategy at this point yet, left for later discussion.
The text was updated successfully, but these errors were encountered: