{"action":"opened","issue":{"url":"https://api.github.com/repos/styladev/stylaguide/issues/5","repository_url":"https://api.github.com/repos/styladev/stylaguide","labels_url":"https://api.github.com/repos/styladev/stylaguide/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/styladev/stylaguide/issues/5/comments","events_url":"https://api.github.com/repos/styladev/stylaguide/issues/5/events","html_url":"https://github.com/styladev/stylaguide/issues/5","id":187011947,"number":5,"title":"Enforce Strict Coding Style vs provide loose Guidelines","user":{"login":"webstrap","id":822694,"avatar_url":"https://avatars.githubusercontent.com/u/822694?v=3","gravatar_id":"","url":"https://api.github.com/users/webstrap","html_url":"https://github.com/webstrap","followers_url":"https://api.github.com/users/webstrap/followers","following_url":"https://api.github.com/users/webstrap/following{/other_user}","gists_url":"https://api.github.com/users/webstrap/gists{/gist_id}","starred_url":"https://api.github.com/users/webstrap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webstrap/subscriptions","organizations_url":"https://api.github.com/users/webstrap/orgs","repos_url":"https://api.github.com/users/webstrap/repos","events_url":"https://api.github.com/users/webstrap/events{/privacy}","received_events_url":"https://api.github.com/users/webstrap/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-03T09:37:41Z","updated_at":"2016-11-03T09:37:41Z","closed_at":null,"body":"This is a more general question not for a certain action.\r\n\r\nDo you prefer rather strict coding styles that defines things as far as possible and tries to enforce it maybe\r\n- define as well things that are just flavor to have a completely unified code base\r\n- break build on style error\r\n- forbid commit broken styles to the repository (commit hooks)\r\n\r\nvs\r\n\r\ndefine things rather with a bit more flexibility, so that people can choose if in doubt which version in a certain situation is more readable\r\n- define the important things and leave other things rather open\r\n- don't break the build but show/report the errors somewhere\r\n- allow to commit things to be maybe messy on your own branch, but set as a rule that master, stage, dev or so should be clean\r\n\r\nThat are just the extremes and not everything has to be done, but just to have a general opinion from everyone on the matter.\r\n\r\nPlease vote below"}}
{"actor":{"display_login":"webstrap"}}