{"action":"created","issue":{"url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/241","labels_url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/241/labels{/name}","comments_url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/241/comments","events_url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/241/events","html_url":"https://github.com/OpenSourcePolicyCenter/Tax-Calculator/issues/241","id":67437718,"number":241,"title":"What is the proper format for \"row_label\" in params.json?","user":{"login":"talumbau","id":1891418,"avatar_url":"https://avatars.githubusercontent.com/u/1891418?v=3","gravatar_id":"","url":"https://api.github.com/users/talumbau","html_url":"https://github.com/talumbau","followers_url":"https://api.github.com/users/talumbau/followers","following_url":"https://api.github.com/users/talumbau/following{/other_user}","gists_url":"https://api.github.com/users/talumbau/gists{/gist_id}","starred_url":"https://api.github.com/users/talumbau/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/talumbau/subscriptions","organizations_url":"https://api.github.com/users/talumbau/orgs","repos_url":"https://api.github.com/users/talumbau/repos","events_url":"https://api.github.com/users/talumbau/events{/privacy}","received_events_url":"https://api.github.com/users/talumbau/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-04-09T19:50:27Z","updated_at":"2015-04-10T18:20:35Z","closed_at":null,"body":"Some values of `row_label` are `[2013, 2014, 2015]`. Some are `[\"2013\", \"2014\", \"2015\"]`. We should be consistent. It is OK if the value for `row_label` is empty (i.e. it is `\"\"`), but if a value is present, it should be consistent. I would advocate for a list of strings, so  `[\"2013\", \"2014\", \"2015\"]`"},"comment":{"url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/comments/91643798","html_url":"https://github.com/OpenSourcePolicyCenter/Tax-Calculator/issues/241#issuecomment-91643798","issue_url":"https://api.github.com/repos/OpenSourcePolicyCenter/Tax-Calculator/issues/241","id":91643798,"user":{"login":"zrisher","id":1958130,"avatar_url":"https://avatars.githubusercontent.com/u/1958130?v=3","gravatar_id":"","url":"https://api.github.com/users/zrisher","html_url":"https://github.com/zrisher","followers_url":"https://api.github.com/users/zrisher/followers","following_url":"https://api.github.com/users/zrisher/following{/other_user}","gists_url":"https://api.github.com/users/zrisher/gists{/gist_id}","starred_url":"https://api.github.com/users/zrisher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zrisher/subscriptions","organizations_url":"https://api.github.com/users/zrisher/orgs","repos_url":"https://api.github.com/users/zrisher/repos","events_url":"https://api.github.com/users/zrisher/events{/privacy}","received_events_url":"https://api.github.com/users/zrisher/received_events","type":"User","site_admin":false},"created_at":"2015-04-10T18:20:35Z","updated_at":"2015-04-10T18:20:35Z","body":"I could see going either way:\r\n\r\nPro string\r\n* it's more likely a consumer of this datapoint would be presenting it than doing math on it\r\n* most of the data in params.json is strings\r\n\r\nPro int\r\n* All of the data in params.json is currently natively typed - true/false, ints, etc. No other field is a type other than its most basic form.\r\n* Slightly smaller data size\r\n\r\nI think the greatest consistency would be achieved by either storing it as an int, or storing it as a string and changing `start_year` to a string. In the former case, you know everything is stored in its most native data type. In the later, you know values/cpi-toggle are stored as their native types and everything else is a string."}}