{"action":"created","issue":{"url":"https://api.github.com/repos/danez/test-import3/issues/2","repository_url":"https://api.github.com/repos/danez/test-import3","labels_url":"https://api.github.com/repos/danez/test-import3/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/danez/test-import3/issues/2/comments","events_url":"https://api.github.com/repos/danez/test-import3/issues/2/events","html_url":"https://github.com/danez/test-import3/issues/2","id":175444001,"number":2,"title":"Implement new decorator proposal when finalized","user":{"login":"danez","id":231804,"avatar_url":"https://avatars.githubusercontent.com/u/231804?v=3","gravatar_id":"","url":"https://api.github.com/users/danez","html_url":"https://github.com/danez","followers_url":"https://api.github.com/users/danez/followers","following_url":"https://api.github.com/users/danez/following{/other_user}","gists_url":"https://api.github.com/users/danez/gists{/gist_id}","starred_url":"https://api.github.com/users/danez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danez/subscriptions","organizations_url":"https://api.github.com/users/danez/orgs","repos_url":"https://api.github.com/users/danez/repos","events_url":"https://api.github.com/users/danez/events{/privacy}","received_events_url":"https://api.github.com/users/danez/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":64,"created_at":"2016-09-07T08:36:19Z","updated_at":"2016-09-07T08:43:01Z","closed_at":null,"body":"asd"},"comment":{"url":"https://api.github.com/repos/danez/test-import3/issues/comments/245214876","html_url":"https://github.com/danez/test-import3/issues/2#issuecomment-245214876","issue_url":"https://api.github.com/repos/danez/test-import3/issues/2","id":245214876,"user":{"login":"danez","id":231804,"avatar_url":"https://avatars.githubusercontent.com/u/231804?v=3","gravatar_id":"","url":"https://api.github.com/users/danez","html_url":"https://github.com/danez","followers_url":"https://api.github.com/users/danez/followers","following_url":"https://api.github.com/users/danez/following{/other_user}","gists_url":"https://api.github.com/users/danez/gists{/gist_id}","starred_url":"https://api.github.com/users/danez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danez/subscriptions","organizations_url":"https://api.github.com/users/danez/orgs","repos_url":"https://api.github.com/users/danez/repos","events_url":"https://api.github.com/users/danez/events{/privacy}","received_events_url":"https://api.github.com/users/danez/received_events","type":"User","site_admin":false},"created_at":"2016-09-07T08:43:01Z","updated_at":"2016-09-07T08:43:01Z","body":"> Comment originally made by loganfsmyth on 2016-04-08T16:36:46.000Z\n\nGeneral FYI, we've currently got two PRs open with approaches to this:\n\n* From me: https://github.com/babel/babel/pull/3331\n* From jmm: https://github.com/babel/babel/pull/3349\n\nNot necessarily sure when we'll next make progress, but this is something we want to do.\n\n<hr />\n\n> Comment originally made by jmm on 2016-04-30T17:28:52.000Z\n\nTo be clear, I think \"presets\" //should// accept options. But, for reasons explained in [my PR](https://github.com/babel/babel/pull/3349), I think that should go along with \"preset\" being a concept and not a public API option. I think in a future major version presets should be merged with plugins so that there comes to be no `presets` option, only a `plugins` option. My understanding, based on discussion on Slack, is that sebmck and loganfsmyth are :thumbsup: on that. I'll create a new issue to track that.\n\nI don't think the API should be changed for presets to accept options without a plan to eventually merge them into the `plugins` option / API and eliminate the `presets` option. So my PR doesn't represent the end result I want to see, it was just a counterpoint to the proposal to do what I just described.\n\nIf things are merged and you can do `plugins: [[\"a-preset-plugin\", {opts: here}]`, maybe it'll still be useful in addition to do what my PR illustrates: construct a plugin package that exports data that can be used to dynamically make a derivative plugin. But that's a separate issue and probably not something Babel's API needs to be concerned with. A preset-like plugin will be responsible for defining what options it accepts and what it does with them, how much it abstracts or exposes configuration of other plugins it contains. It could also provide a means to expose data about it's internal configuration (e.g. array of plugin names and options) separately from Babel's options API or even piggybacked on it (e.g. `config = require(\"some-preset-plugin\")({returnConfig: true})` where `returnConfig` is just an option the plugin has elected to provide).\n\nFor \"official\" plugins decisions would have to be made about what options to provide and how much to expose to strike an appropriate balance between customizability and not setting people up with footguns. If it's overconstrained there will still be a bunch of slightly different derivative plugins created and published and more frequent feature requests to provide some additional dimension of customizability that have to be handled by the maintainers.\n\n\n\n<hr />\n\n> Comment originally made by hzoo on 2016-08-04T23:44:50.000Z\n\nAdded in https://github.com/babel/babel/pull/3331 in https://github.com/babel/babel/releases/tag/v6.13.0"}}
{"actor":{"display_login":"danez"}}