{"action":"created","issue":{"url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/107","repository_url":"https://api.github.com/repos/smarthomeNG/smarthome","labels_url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/107/labels{/name}","comments_url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/107/comments","events_url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/107/events","html_url":"https://github.com/smarthomeNG/smarthome/pull/107","id":172212951,"number":107,"title":"Implemented support for item configuration files in yaml","user":{"login":"msinn","id":452067,"avatar_url":"https://avatars.githubusercontent.com/u/452067?v=3","gravatar_id":"","url":"https://api.github.com/users/msinn","html_url":"https://github.com/msinn","followers_url":"https://api.github.com/users/msinn/followers","following_url":"https://api.github.com/users/msinn/following{/other_user}","gists_url":"https://api.github.com/users/msinn/gists{/gist_id}","starred_url":"https://api.github.com/users/msinn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msinn/subscriptions","organizations_url":"https://api.github.com/users/msinn/orgs","repos_url":"https://api.github.com/users/msinn/repos","events_url":"https://api.github.com/users/msinn/events{/privacy}","received_events_url":"https://api.github.com/users/msinn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2016-08-19T20:22:20Z","updated_at":"2016-09-11T18:00:33Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/smarthomeNG/smarthome/pulls/107","html_url":"https://github.com/smarthomeNG/smarthome/pull/107","diff_url":"https://github.com/smarthomeNG/smarthome/pull/107.diff","patch_url":"https://github.com/smarthomeNG/smarthome/pull/107.patch"},"body":"Hi,\r\n\r\nI implemented yaml support for configuration files. At this stage of the game, I activated it for item config files.\r\n\r\nThe benefits of yaml configuration files:\r\n- standard file format\r\n- easier to modifiy, specially if you are moving blocks of items around (changing nesting levels)\r\n- easier to modifiy in some text editors (like TextWrangler on Mac): You can fold parts of the file you don't edit\r\n- file format is easier to read/parse and to write by programs (eg. in the future for an item editor)\r\n\r\nYou can stay with your .conf files or use .yaml files or use a mix of .conf and .yaml files in the ../items folder.\r\n\r\nI have added a converter, that converts existing .conf files to .yaml files:\r\nTo start the converter, change to the ../tools folder and start \r\n```\r\n    cd tools\r\n    python3 item_conf_to_yaml_converter.py\r\n```\r\n\r\nThe converter creates a .yaml file for every .conf file it finds in the ../items folder. After it finishes, move all .conf files to a different folder (to have a backup, just in case...). Otherwise all item definitions would be processed twice when you restart SmartHomeNG, because SmartHomeNG now processes **all** .conf files and **all** .yaml files it finds in the ../items folder. \r\n\r\nIt works nicely with my 43 item-configuration files (about 1500 items)."},"comment":{"url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/comments/246194057","html_url":"https://github.com/smarthomeNG/smarthome/pull/107#issuecomment-246194057","issue_url":"https://api.github.com/repos/smarthomeNG/smarthome/issues/107","id":246194057,"user":{"login":"ohinckel","id":717217,"avatar_url":"https://avatars.githubusercontent.com/u/717217?v=3","gravatar_id":"","url":"https://api.github.com/users/ohinckel","html_url":"https://github.com/ohinckel","followers_url":"https://api.github.com/users/ohinckel/followers","following_url":"https://api.github.com/users/ohinckel/following{/other_user}","gists_url":"https://api.github.com/users/ohinckel/gists{/gist_id}","starred_url":"https://api.github.com/users/ohinckel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ohinckel/subscriptions","organizations_url":"https://api.github.com/users/ohinckel/orgs","repos_url":"https://api.github.com/users/ohinckel/repos","events_url":"https://api.github.com/users/ohinckel/events{/privacy}","received_events_url":"https://api.github.com/users/ohinckel/received_events","type":"User","site_admin":false},"created_at":"2016-09-11T18:00:33Z","updated_at":"2016-09-11T18:00:33Z","body":"@msinn usually you can fetch the latest verson of the develop branch (from origin or vendor or whatever you uses as name for the remote of shng repo) and merge it using `git merge develop`. As far as I see you also named your local branch develop and it`s remote tracking branch could be the develop branch of shng - in this case it should be enough to use `git pull`.\r\n\r\nIt all depend on your setup - if nothing works just let me know. I'll fetch your branch and bing them up to date to create a new PR."}}
{"actor":{"display_login":"ohinckel"}}