{"action":"opened","issue":{"url":"https://api.github.com/repos/blevesearch/bleve/issues/278","labels_url":"https://api.github.com/repos/blevesearch/bleve/issues/278/labels{/name}","comments_url":"https://api.github.com/repos/blevesearch/bleve/issues/278/comments","events_url":"https://api.github.com/repos/blevesearch/bleve/issues/278/events","html_url":"https://github.com/blevesearch/bleve/issues/278","id":117282361,"number":278,"title":"add JSON marshalers for built-in analysis components","user":{"login":"steveyen","id":30640,"avatar_url":"https://avatars.githubusercontent.com/u/30640?v=3","gravatar_id":"","url":"https://api.github.com/users/steveyen","html_url":"https://github.com/steveyen","followers_url":"https://api.github.com/users/steveyen/followers","following_url":"https://api.github.com/users/steveyen/following{/other_user}","gists_url":"https://api.github.com/users/steveyen/gists{/gist_id}","starred_url":"https://api.github.com/users/steveyen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/steveyen/subscriptions","organizations_url":"https://api.github.com/users/steveyen/orgs","repos_url":"https://api.github.com/users/steveyen/repos","events_url":"https://api.github.com/users/steveyen/events{/privacy}","received_events_url":"https://api.github.com/users/steveyen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-17T04:56:08Z","updated_at":"2015-11-17T04:56:08Z","closed_at":null,"body":"(On Marty's suggestion, I converted an email into a public github issues...)\r\n\r\nI'd started looking at how to get bleve's built-in analysis components into the bleve-mapping-ui project....\r\n\r\nThey're all listed in bleve's registry, so that's good.  But, what I need (I think) next is a way to get some JSON representation for *some* of these various built-in components, to be able to send to the browser/UI.\r\n\r\nThe idea is that a user of bleve-mapping-ui should just be able to click some sort of copy or clone button on some existing built-in analysis components in order to use that as a starting point for their own, fancy custom definitions.\r\n\r\nSo, I think the next step is to start adding JSON marshaling code to some of these things (the data-driven ones, like token maps)... and, to the ones that are JSON amendable (not all of them are).  But, of course need Marty's sanity check that this is viable, and useful, and isn't an offensive, or waste-of-time pathway.\r\n"}}