{"action":"closed","issue":{"url":"https://api.github.com/repos/nicksergeant/snipt/issues/148","labels_url":"https://api.github.com/repos/nicksergeant/snipt/issues/148/labels{/name}","comments_url":"https://api.github.com/repos/nicksergeant/snipt/issues/148/comments","events_url":"https://api.github.com/repos/nicksergeant/snipt/issues/148/events","html_url":"https://github.com/nicksergeant/snipt/issues/148","id":66420126,"number":148,"title":"custom properties for snipts","user":{"login":"jeanfabre","id":1140265,"avatar_url":"https://avatars.githubusercontent.com/u/1140265?v=3","gravatar_id":"","url":"https://api.github.com/users/jeanfabre","html_url":"https://github.com/jeanfabre","followers_url":"https://api.github.com/users/jeanfabre/followers","following_url":"https://api.github.com/users/jeanfabre/following{/other_user}","gists_url":"https://api.github.com/users/jeanfabre/gists{/gist_id}","starred_url":"https://api.github.com/users/jeanfabre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeanfabre/subscriptions","organizations_url":"https://api.github.com/users/jeanfabre/orgs","repos_url":"https://api.github.com/users/jeanfabre/repos","events_url":"https://api.github.com/users/jeanfabre/events{/privacy}","received_events_url":"https://api.github.com/users/jeanfabre/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-05T09:23:38Z","updated_at":"2015-04-06T15:02:06Z","closed_at":"2015-04-06T15:02:06Z","body":"Hi,\r\n\r\nFirst of all, diving more and more into your system, I think I found a real gem, thanks for your amazing work! \r\n\r\nI think a snipt with custom meta data would be truly unleashing potential, so that author can define custom properties. Right now, It's either we embed this meta data into the snipt itself or we use the description field, but I think it's not very clean. Typically, I see \"tags\" and \"user\" in the json object for a snipt. It would be great to have a \"MetaData\" or \"Custom\" additional/optional object, so that we can create our own context for snipt. \r\n\r\nI think it doesn't even need to be in the visual interface you present on the web application, but something that can be set with the api as a json, because this kind of feature typically make sense when integrating snipt as the source for content for applications.\r\n\r\nRegards,\r\n\r\n Jean\r\n\r\n"}}