{"action":"created","issue":{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/34","labels_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/34/comments","events_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/34/events","html_url":"https://github.com/Semantic-Org/Semantic-UI-Meteor/issues/34","id":94573729,"number":34,"title":"BUG: can not find site.variables","user":{"login":"Chun-Yang","id":2827867,"avatar_url":"https://avatars.githubusercontent.com/u/2827867?v=3","gravatar_id":"","url":"https://api.github.com/users/Chun-Yang","html_url":"https://github.com/Chun-Yang","followers_url":"https://api.github.com/users/Chun-Yang/followers","following_url":"https://api.github.com/users/Chun-Yang/following{/other_user}","gists_url":"https://api.github.com/users/Chun-Yang/gists{/gist_id}","starred_url":"https://api.github.com/users/Chun-Yang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Chun-Yang/subscriptions","organizations_url":"https://api.github.com/users/Chun-Yang/orgs","repos_url":"https://api.github.com/users/Chun-Yang/repos","events_url":"https://api.github.com/users/Chun-Yang/events{/privacy}","received_events_url":"https://api.github.com/users/Chun-Yang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-07-12T15:29:24Z","updated_at":"2015-09-07T19:34:58Z","closed_at":null,"body":"Thank you for your awesome package.\r\n\r\nWhen I edit custom.semantic.json,\r\n```\r\nthemes: {\r\n  // ...\r\n  \"default\": false,\r\n  \"classic\": true,\r\n  // ...\r\n}\r\n```\r\nI get error:\r\n```\r\nWhile building the application:\r\n   client/semantic-ui/theme.import.less:17:1: Less compiler error:\r\n   'themes/default/globals/site.variables' wasn't found. Tried -\r\n   client/semantic-ui/themes/default/globals/site.variables,\r\n   /Users/trent/Work/tax/client/semantic-ui/themes/default/globals/site.variables,\r\n   /Users/trent/Work/tax/themes/default/globals/site.variables,\r\n   themes/default/globals/site.variables\r\n```\r\nBut when I change default to true, everything works. Does it mean I ALWAYS need to turn default to true?"},"comment":{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/comments/138365756","html_url":"https://github.com/Semantic-Org/Semantic-UI-Meteor/issues/34#issuecomment-138365756","issue_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI-Meteor/issues/34","id":138365756,"user":{"login":"giantelk","id":6137169,"avatar_url":"https://avatars.githubusercontent.com/u/6137169?v=3","gravatar_id":"","url":"https://api.github.com/users/giantelk","html_url":"https://github.com/giantelk","followers_url":"https://api.github.com/users/giantelk/followers","following_url":"https://api.github.com/users/giantelk/following{/other_user}","gists_url":"https://api.github.com/users/giantelk/gists{/gist_id}","starred_url":"https://api.github.com/users/giantelk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/giantelk/subscriptions","organizations_url":"https://api.github.com/users/giantelk/orgs","repos_url":"https://api.github.com/users/giantelk/repos","events_url":"https://api.github.com/users/giantelk/events{/privacy}","received_events_url":"https://api.github.com/users/giantelk/received_events","type":"User","site_admin":false},"created_at":"2015-09-07T19:34:58Z","updated_at":"2015-09-07T19:34:58Z","body":"@micktaiwan Is it possible you did not remove the file `.custom.semantic.json`\r\n\r\n`Note: if you are happy with the default values you will need to remove .custom.semantic.json to generate Semantic UI. (see Generating Trigger)` \r\nhttps://atmospherejs.com/semantic/ui\r\n\r\nThis step caught me too, I missed it. Ideally you should not have to remove files to get the default behavior. \r\n\r\nAlso, if the default theme needs to be true at ALL times, there should not be any option to set it to false. IMHO it's not good for usability/ease of use to show/provide options that aren't really options...(key being \"options that aren't options\"). At the very least add a comment to the JSON file like:\r\n\r\n```\r\n\"default\": true, // The default option MUST ALWAYS be set to true. Setting default to false will cause zero themes to load.\r\n```\r\n\r\nSince comments aren't supported in JSON, could also hack the comment:\r\n```\r\n\"default\": true, \r\n\"comment_default\": \"The default option MUST ALWAYS be set to true. Setting default to false will cause zero themes to load.\"\r\n```\r\n\r\nMore info on comments in JSON files and various workarounds:\r\nhttp://stackoverflow.com/questions/244777/can-i-comment-a-json-file\r\n"}}