{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/d9cdf9d9857c1064b77ae6ac8cd03dfd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d9cdf9d9857c1064b77ae6ac8cd03dfd","url":"https://api.github.com/users/klipstein","login":"klipstein","id":158866},"assignee":null,"updated_at":"2011-11-14T19:28:34Z","labels":[],"closed_at":null,"comments":9,"url":"https://api.github.com/repos/evilhackerdude/syntux/issues/3","body":"In the README.md there is a mention that syntux should also include warnings if classes, functions and constants aren't named as defined in the coding styles. I would remove these lines from the README as it gives the notion that it will also check the code for inconsistencies.\r\n\r\nMaybe a good rule would be, that syntux is a tool for changing code when it is able to modify it without changing the original behaviour of it. For now I would try to avoid outputting warnings of possible coding style conflicts, as they could lead to a huge list of configuration options for the syntux/config.json file.\r\n\r\nI could help out defining the syntux configuration file.\r\n\r\n\r\n\r\n","html_url":"https://github.com/evilhackerdude/syntux/issues/3","title":"Narrow down the usecase of syntux","number":3,"id":2050101,"created_at":"2011-10-25T21:24:41Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/d9cdf9d9857c1064b77ae6ac8cd03dfd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d9cdf9d9857c1064b77ae6ac8cd03dfd","url":"https://api.github.com/users/klipstein","login":"klipstein","id":158866},"updated_at":"2011-11-14T19:28:34Z","url":"https://api.github.com/repos/evilhackerdude/syntux/issues/comments/2735216","body":"I'm just sitting in front of implementing some more plugins for syntux and I currently looking into whitespacing / brace-styling. For inspiration I've looked into http://jalopy.sourceforge.net/existing/whitespace.html and http://jalopy.sourceforge.net/existing/braces.html.\r\n\r\nDifferent brace styles could be defined with the following configuration:\r\n\r\n~~~json\r\n{\r\n  /* definition as array (cStyle) */\r\n  \"braces\": [\"{\", \"\\n}\"],\r\n  /* or: definition as array (sunStyle) */\r\n \"braces\": [\"\\n{\", \"\\n}\"],\r\n  /* or: definition as array (gnuStyle) */\r\n  \"braces\": [\"\\n  {\", \"\\n  }\"],\r\n  /* or: defintion by name */\r\n  \"braces\": \"cStyle\" /* or: \"sunStyle\", \"gnuStyle\" */\r\n}\r\n~~~\r\n\r\nThe configuration for whitespaces could look like that:\r\n\r\n~~~json\r\n{\r\n  \"whitespace\": {\r\n    \"spaceBefore\": {\r\n      \"methodDeclaration\": true, /* false */\r\n      \"methodCall\": true,\r\n      \"statement\": true,\r\n      \"braces\": true,\r\n      \"brackets\": true,\r\n      \"caseColon\": true\r\n    },\r\n    \"spaceAfter\": {\r\n      \"comma\": true,\r\n      \"semicolon\": true,\r\n      \"logicalNot\": true\r\n    },\r\n    \"spacesAround\": {\r\n       \"assignmentOp\": true,\r\n       \"logicalOp\": true,\r\n       \"relationalOp\": true,\r\n       \"bitwiseOp\": true,\r\n       \"mathOp\": true,\r\n       \"shiftOp\": true,\r\n       \"braces\": true,\r\n       \"brackets\": true,\r\n       \"parantheses\": true\r\n    }\r\n}\r\n~~~\r\n\r\nTo configure it more easily we could define some common rules (same as with `braces` above):\r\n\r\n~~~json\r\n{\r\n  \"whitespace\": \"nodeStyle\",\r\n  /* or */\r\n  \"whitespace\": \"dojoStyle\"\r\n}\r\n~~~\r\n","id":2735216,"created_at":"2011-11-14T19:28:34Z"}}