{"action":"created","issue":{"url":"https://api.github.com/repos/mixu/markdown-styles/issues/22","labels_url":"https://api.github.com/repos/mixu/markdown-styles/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/mixu/markdown-styles/issues/22/comments","events_url":"https://api.github.com/repos/mixu/markdown-styles/issues/22/events","html_url":"https://github.com/mixu/markdown-styles/issues/22","id":94034146,"number":22,"title":"using meta.json","user":{"login":"parmentelat","id":4519227,"avatar_url":"https://avatars.githubusercontent.com/u/4519227?v=3","gravatar_id":"","url":"https://api.github.com/users/parmentelat","html_url":"https://github.com/parmentelat","followers_url":"https://api.github.com/users/parmentelat/followers","following_url":"https://api.github.com/users/parmentelat/following{/other_user}","gists_url":"https://api.github.com/users/parmentelat/gists{/gist_id}","starred_url":"https://api.github.com/users/parmentelat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/parmentelat/subscriptions","organizations_url":"https://api.github.com/users/parmentelat/orgs","repos_url":"https://api.github.com/users/parmentelat/repos","events_url":"https://api.github.com/users/parmentelat/events{/privacy}","received_events_url":"https://api.github.com/users/parmentelat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-07-09T12:23:25Z","updated_at":"2015-07-14T20:59:11Z","closed_at":null,"body":"Hi there\r\n\r\nFirst off, many thanks for putting this together ! Looks like a really cool idea and I got my micro website up and running in an eye blink :)\r\n\r\nI'm at the point where I'd need to leverage this meta.json business.\r\nIt first took me some time to figure I had to install it inside the input/ directory\r\nafter I instrumented the code I can see now that my file is read all right, but the corresponding {{foo}} replacements do not take place, and I am trying to figure out what it is that I do wrong\r\n\r\nI guess there is some confusion in my mind as to what is expected in that dictionary. The doc at https://github.com/mixu/markdown-styles#metajson explains how to define variable repoUrl for files under input/foo; what about files at the toplevel right in input/ ?\r\n\r\nI have tried various tricks for defining 'bar' like\r\n{\r\n  \"\" : { 'bar' : 'value'},\r\n \".\" : { 'bar' : 'value'},\r\n 'bar' : 'value',\r\n'input' : { 'bar' : 'value'},\r\n}\r\n\r\nbut apparently to no avail, the occurrences of {{bar}} all come up empty; \r\nI can feel there is something I do just wrong but I can't spot it, can you please help ?\r\n\r\n---\r\nBesides, given this scoping mechanism, I would fancy there should be a means to define a given variable at different levels of the filesystem tree, with the most precise (the longest prefix) taking precedence, is it the case right now ? \r\nI have net yet taken the step of splitting my inputs into subdirs, but if that feature was working as I describe I might go down this road later on.\r\n\r\nThanks again in any case "},"comment":{"url":"https://api.github.com/repos/mixu/markdown-styles/issues/comments/121384600","html_url":"https://github.com/mixu/markdown-styles/issues/22#issuecomment-121384600","issue_url":"https://api.github.com/repos/mixu/markdown-styles/issues/22","id":121384600,"user":{"login":"mixu","id":398530,"avatar_url":"https://avatars.githubusercontent.com/u/398530?v=3","gravatar_id":"","url":"https://api.github.com/users/mixu","html_url":"https://github.com/mixu","followers_url":"https://api.github.com/users/mixu/followers","following_url":"https://api.github.com/users/mixu/following{/other_user}","gists_url":"https://api.github.com/users/mixu/gists{/gist_id}","starred_url":"https://api.github.com/users/mixu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mixu/subscriptions","organizations_url":"https://api.github.com/users/mixu/orgs","repos_url":"https://api.github.com/users/mixu/repos","events_url":"https://api.github.com/users/mixu/events{/privacy}","received_events_url":"https://api.github.com/users/mixu/received_events","type":"User","site_admin":false},"created_at":"2015-07-14T20:59:11Z","updated_at":"2015-07-14T20:59:11Z","body":"Sounds good to me - I think its OK to move away from the legacy mechanism (which was somewhat limited) since I think the migration will be fairly straightforward and I'm pretty sure the people who wanted to move to the 2.x releases have done so by now. \r\n\r\nI like the second naming convention a bit more, since it's closer to how glob expressions are written. I probably won't have too much time to work on this soonish but it's good to have something specced out. \r\n\r\nAs for integration tests, this test can probably be extended a bit to cover the new cases https://github.com/mixu/markdown-styles/blob/master/test/integration.test.js#L71"}}