{"action":"created","issue":{"url":"https://api.github.com/repos/commandlineparser/commandline/issues/198","repository_url":"https://api.github.com/repos/commandlineparser/commandline","labels_url":"https://api.github.com/repos/commandlineparser/commandline/issues/198/labels{/name}","comments_url":"https://api.github.com/repos/commandlineparser/commandline/issues/198/comments","events_url":"https://api.github.com/repos/commandlineparser/commandline/issues/198/events","html_url":"https://github.com/commandlineparser/commandline/issues/198","id":279845935,"number":198,"title":"Enums are not case insensitive","user":{"login":"vmelamed","id":779687,"avatar_url":"https://avatars3.githubusercontent.com/u/779687?v=4","gravatar_id":"","url":"https://api.github.com/users/vmelamed","html_url":"https://github.com/vmelamed","followers_url":"https://api.github.com/users/vmelamed/followers","following_url":"https://api.github.com/users/vmelamed/following{/other_user}","gists_url":"https://api.github.com/users/vmelamed/gists{/gist_id}","starred_url":"https://api.github.com/users/vmelamed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vmelamed/subscriptions","organizations_url":"https://api.github.com/users/vmelamed/orgs","repos_url":"https://api.github.com/users/vmelamed/repos","events_url":"https://api.github.com/users/vmelamed/events{/privacy}","received_events_url":"https://api.github.com/users/vmelamed/received_events","type":"User","site_admin":false},"labels":[{"id":740599276,"url":"https://api.github.com/repos/commandlineparser/commandline/labels/bug","name":"bug","color":"ee0701","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-12-06T17:46:37Z","updated_at":"2018-03-19T00:33:54Z","closed_at":null,"author_association":"NONE","body":"First off: great job, guys!\r\n\r\nSmall issue: it looks like even though the wiki states that option properties bound to enum values are case insensitive:\r\n\r\n> When specifying enum values, you don't need to respect case. Both app -g bye and app --greet-type REGARDS are allowed.\r\n\r\nunfortunately, they are not. I have a program that for a line like this:\r\n```\r\nsettings -s gogo -v 23 -t int\r\n```\r\nwhere -t is bound to an  `enum SettingType {Int, String, ...}`, I get an error:\r\n```\r\nERROR(S):\r\n  Option 't, type' is defined with a bad format.\r\n\r\n  -s, --setting      The name of a setting to be added or modified.\r\n\r\n  -v, --value        The new value of the setting. The option is required if -s or --setting is specified.\r\n\r\n  -t, --type         (Default: String) The case-sensitive type of the value of the setting. The option is not mandatory and if not specified, the\r\n                     type will be either implied from the existing setting with the same name or it will be assumed to be 'String'. The most common\r\n                     types are: String, Int, Guid, Decimal, Boolean, DateTime, Date, Time, Uri, TimeSpan. DateTime values are assumed to be UTC.\r\n\r\n[...etc]\r\n\r\nBadFormatConversionError\r\n  StopsProcessing          = False\r\n  Tag                      = ErrorType.BadFormatConversionError\r\n  NameInfo                 = NameInfo\r\n    LongName                 = type\r\n    NameText                 = t, type\r\n    ShortName                = t\r\n```\r\n\r\nBut if I enter the command like this:\r\n```\r\nsettings -s gogo -v 23 -t Int\r\n```\r\nall is good."},"comment":{"url":"https://api.github.com/repos/commandlineparser/commandline/issues/comments/374071081","html_url":"https://github.com/commandlineparser/commandline/issues/198#issuecomment-374071081","issue_url":"https://api.github.com/repos/commandlineparser/commandline/issues/198","id":374071081,"user":{"login":"mleenhardt","id":8008842,"avatar_url":"https://avatars2.githubusercontent.com/u/8008842?v=4","gravatar_id":"","url":"https://api.github.com/users/mleenhardt","html_url":"https://github.com/mleenhardt","followers_url":"https://api.github.com/users/mleenhardt/followers","following_url":"https://api.github.com/users/mleenhardt/following{/other_user}","gists_url":"https://api.github.com/users/mleenhardt/gists{/gist_id}","starred_url":"https://api.github.com/users/mleenhardt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mleenhardt/subscriptions","organizations_url":"https://api.github.com/users/mleenhardt/orgs","repos_url":"https://api.github.com/users/mleenhardt/repos","events_url":"https://api.github.com/users/mleenhardt/events{/privacy}","received_events_url":"https://api.github.com/users/mleenhardt/received_events","type":"User","site_admin":false},"created_at":"2018-03-19T00:33:54Z","updated_at":"2018-03-19T00:33:54Z","author_association":"NONE","body":"I'm running into the same issue, any chance the fix in #231 could be merged?"}}
{"actor":{"display_login":"mleenhardt"}}