{"action":"created","issue":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/63","repository_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy","labels_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/63/labels{/name}","comments_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/63/comments","events_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/63/events","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/63","id":293566521,"number":63,"title":"Split config files","user":{"login":"thuantran","id":410960,"avatar_url":"https://avatars0.githubusercontent.com/u/410960?v=4","gravatar_id":"","url":"https://api.github.com/users/thuantran","html_url":"https://github.com/thuantran","followers_url":"https://api.github.com/users/thuantran/followers","following_url":"https://api.github.com/users/thuantran/following{/other_user}","gists_url":"https://api.github.com/users/thuantran/gists{/gist_id}","starred_url":"https://api.github.com/users/thuantran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thuantran/subscriptions","organizations_url":"https://api.github.com/users/thuantran/orgs","repos_url":"https://api.github.com/users/thuantran/repos","events_url":"https://api.github.com/users/thuantran/events{/privacy}","received_events_url":"https://api.github.com/users/thuantran/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-01T15:13:40Z","updated_at":"2018-02-01T16:16:56Z","closed_at":null,"author_association":"NONE","body":"Hi Frank,\r\n\r\nJust updated my installer script for asuswrt-merlin users with rc, and it's working great.\r\nI'm considering parsing toml from linux shell, the normal variable and array are fine but it's too much of a hassle with tables and you keep adding more lol.\r\n\r\nSo I wonder if it would be better if you split your configuration file into multiple files for these tables by purpose or whatever make sense to me. That would make it easier on me and on my users to migrate settings between version.\r\n\r\nBest regards,\r\nThuan"},"comment":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/comments/362317184","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/63#issuecomment-362317184","issue_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/63","id":362317184,"user":{"login":"jedisct1","id":124872,"avatar_url":"https://avatars2.githubusercontent.com/u/124872?v=4","gravatar_id":"","url":"https://api.github.com/users/jedisct1","html_url":"https://github.com/jedisct1","followers_url":"https://api.github.com/users/jedisct1/followers","following_url":"https://api.github.com/users/jedisct1/following{/other_user}","gists_url":"https://api.github.com/users/jedisct1/gists{/gist_id}","starred_url":"https://api.github.com/users/jedisct1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jedisct1/subscriptions","organizations_url":"https://api.github.com/users/jedisct1/orgs","repos_url":"https://api.github.com/users/jedisct1/repos","events_url":"https://api.github.com/users/jedisct1/events{/privacy}","received_events_url":"https://api.github.com/users/jedisct1/received_events","type":"User","site_admin":false},"created_at":"2018-02-01T16:16:56Z","updated_at":"2018-02-01T16:16:56Z","author_association":"OWNER","body":"Reading TOML (or even JSON or any structured format) from shell scripts sounds fragile.\r\n\r\nTools such as [`tomlq`](https://github.com/jamesmunns/tomlq) and [`rq`](https://github.com/dflemstr/rq) are great for that purpose, but requiring them is probably overkill if they aren't already present in a minimal Linux distribution.\r\n\r\nHaving everything in a single file is convenient. If you add a static definition, you can easily copy/paste the name to the `resolver_names` above; all is in the same place.\r\n\r\nI'm not sure that splitting it into multiple files would make parsing in shell easier. Nested values such as the weekly schedules will still be as tricky to parse.\r\n\r\nIf you parse the file line by line, you can spot the different sections with something like\r\n\r\n```\r\negrep '^\\s*\\[[^.]+\\]'\r\n```"}}
{"actor":{"display_login":"jedisct1"}}