Persistent solution-level configuration #7
Description
Background
Persisting solution-specific configuration information (such as the names of test projects excluded from mapping) will simplify Iceberg's UX by removing the need to manually load the solution each time Iceberg is run and will cut down on the number of CLI options that need to be provided with mapping-related commands.
Possible Solution
Add a new init command that generates an iceberg.json config file in the solution directory. When starting an Iceberg session check if an iceberg.json file exists in the working directory. If one exists, use the configuration settings specified in it and automatically load the associated solution on launch (to remove the need for manually loading the solution with the load command).
Possible Settings
- Name of or relative path to the associated solution file
- List of excluded project names (to be used by project exclusion filter)
- Relative path to the desired output directory for generated code maps