{"action":"created","issue":{"url":"https://api.github.com/repos/yahoo/flux-examples/issues/102","labels_url":"https://api.github.com/repos/yahoo/flux-examples/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/yahoo/flux-examples/issues/102/comments","events_url":"https://api.github.com/repos/yahoo/flux-examples/issues/102/events","html_url":"https://github.com/yahoo/flux-examples/issues/102","id":56928574,"number":102,"title":"getting component context inside the component","user":{"login":"trungpham","id":149616,"avatar_url":"https://avatars.githubusercontent.com/u/149616?v=3","gravatar_id":"","url":"https://api.github.com/users/trungpham","html_url":"https://github.com/trungpham","followers_url":"https://api.github.com/users/trungpham/followers","following_url":"https://api.github.com/users/trungpham/following{/other_user}","gists_url":"https://api.github.com/users/trungpham/gists{/gist_id}","starred_url":"https://api.github.com/users/trungpham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trungpham/subscriptions","organizations_url":"https://api.github.com/users/trungpham/orgs","repos_url":"https://api.github.com/users/trungpham/repos","events_url":"https://api.github.com/users/trungpham/events{/privacy}","received_events_url":"https://api.github.com/users/trungpham/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-02-07T22:23:10Z","updated_at":"2015-02-13T00:56:20Z","closed_at":"2015-02-12T23:14:57Z","body":"I have a plugin that populate the component context, however, I am not able to access the component context.\r\nThough, after mixing in the fluxible,Mixin. I can see context.executionAction, and context.getStore just fine.\r\n\r\nDo you know how I can get the access to the component Context that populated by my plugin? Thanks."},"comment":{"url":"https://api.github.com/repos/yahoo/flux-examples/issues/comments/74186197","html_url":"https://github.com/yahoo/flux-examples/issues/102#issuecomment-74186197","issue_url":"https://api.github.com/repos/yahoo/flux-examples/issues/102","id":74186197,"user":{"login":"lingyan","id":1414235,"avatar_url":"https://avatars.githubusercontent.com/u/1414235?v=3","gravatar_id":"","url":"https://api.github.com/users/lingyan","html_url":"https://github.com/lingyan","followers_url":"https://api.github.com/users/lingyan/followers","following_url":"https://api.github.com/users/lingyan/following{/other_user}","gists_url":"https://api.github.com/users/lingyan/gists{/gist_id}","starred_url":"https://api.github.com/users/lingyan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lingyan/subscriptions","organizations_url":"https://api.github.com/users/lingyan/orgs","repos_url":"https://api.github.com/users/lingyan/repos","events_url":"https://api.github.com/users/lingyan/events{/privacy}","received_events_url":"https://api.github.com/users/lingyan/received_events","type":"User","site_admin":false},"created_at":"2015-02-13T00:56:20Z","updated_at":"2015-02-13T00:56:20Z","body":"From another angle, it is better for each component that uses context function(s) to define contextTypes inside the component, without the plugin providing a mixin for this purpose only.    When the plugin provides a mixin, the mixin can't really predict which function(s) is needed by a component, and whether they should be mandatory or optional.   So it is actually better for the components themselves to define contextTypes as part of its spec."}}