Issue by stempelj
Wednesday Apr 13, 2016 at 00:36 GMT
Originally opened as gsscoder/commandline#303
Currently, the only way to supply a list of valid verbs is through attributes. Adding support for explicitly defining verbs via settings will provide a clean solution when there is not a lot of variation between sub-parameters of verbs. For example:
CommonOptions supports -a and -b
UniqueOperationOptions supports verb -c
Currently, a developer must create empty but verb-attributed classes to support other verbs that only care about -a and -b. Ideally, one could supply a list of verbs via code, or alternatively by supplying multiple verb names via CommonOptions' verb attributes.
Note: Inheritance is supported, which prevents duplication of the definitions of -a and -b, but it does not address the extraneous class issue.
Wednesday Apr 13, 2016 at 00:36 GMT
Originally opened as gsscoder/commandline#303
Currently, the only way to supply a list of valid verbs is through attributes. Adding support for explicitly defining verbs via settings will provide a clean solution when there is not a lot of variation between sub-parameters of verbs. For example:
CommonOptions supports -a and -b
UniqueOperationOptions supports verb -c
Currently, a developer must create empty but verb-attributed classes to support other verbs that only care about -a and -b. Ideally, one could supply a list of verbs via code, or alternatively by supplying multiple verb names via CommonOptions' verb attributes.
Note: Inheritance is supported, which prevents duplication of the definitions of -a and -b, but it does not address the extraneous class issue.