This was first mentioned on ticket #205, but if we stored the actual options in a generator then we could very easily implement methods to check if a generator was run with a specific option. All existing methods would be useable as is, since the generator's option string is created in the options class itself already.
If a generator is run with no options, and provides default values in this case, then currently the options class doesn't store the defualt value. We could change this behaviour so that if a default value is returned (since the requested option was specified) we create a key value pair as if the option had been specified in the config file.
Things that would need (re)implementing:
Getters for the value of the individual underlying options given to a generator.
Assigning / Constructing from a string would need to be re-interpreted to recreate an options instance.
If default options are used by a generator, add this into the options instance key-value map.
This was first mentioned on ticket #205, but if we stored the actual options in a generator then we could very easily implement methods to check if a generator was run with a specific option. All existing methods would be useable as is, since the generator's option string is created in the options class itself already.
If a generator is run with no options, and provides default values in this case, then currently the options class doesn't store the defualt value. We could change this behaviour so that if a default value is returned (since the requested option was specified) we create a key value pair as if the option had been specified in the config file.
Things that would need (re)implementing: