{"action":"created","issue":{"url":"https://api.github.com/repos/kadirahq/react-komposer/issues/111","repository_url":"https://api.github.com/repos/kadirahq/react-komposer","labels_url":"https://api.github.com/repos/kadirahq/react-komposer/issues/111/labels{/name}","comments_url":"https://api.github.com/repos/kadirahq/react-komposer/issues/111/comments","events_url":"https://api.github.com/repos/kadirahq/react-komposer/issues/111/events","html_url":"https://github.com/kadirahq/react-komposer/issues/111","id":169171671,"number":111,"title":"Get rid of null in onData(null)","user":{"login":"ElegantSudo","id":19272022,"avatar_url":"https://avatars.githubusercontent.com/u/19272022?v=3","gravatar_id":"","url":"https://api.github.com/users/ElegantSudo","html_url":"https://github.com/ElegantSudo","followers_url":"https://api.github.com/users/ElegantSudo/followers","following_url":"https://api.github.com/users/ElegantSudo/following{/other_user}","gists_url":"https://api.github.com/users/ElegantSudo/gists{/gist_id}","starred_url":"https://api.github.com/users/ElegantSudo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ElegantSudo/subscriptions","organizations_url":"https://api.github.com/users/ElegantSudo/orgs","repos_url":"https://api.github.com/users/ElegantSudo/repos","events_url":"https://api.github.com/users/ElegantSudo/events{/privacy}","received_events_url":"https://api.github.com/users/ElegantSudo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-08-03T16:12:46Z","updated_at":"2016-08-06T17:28:25Z","closed_at":null,"body":"The  is first argument, which is almost always defined as `null` in the `onData()` function is not used by the majority of developers and only adds confusion to the package.\r\n\r\nI've met a couple of developers who seriously want to punch their computer because the null is so unnecessary."},"comment":{"url":"https://api.github.com/repos/kadirahq/react-komposer/issues/comments/238035083","html_url":"https://github.com/kadirahq/react-komposer/issues/111#issuecomment-238035083","issue_url":"https://api.github.com/repos/kadirahq/react-komposer/issues/111","id":238035083,"user":{"login":"ElegantSudo","id":19272022,"avatar_url":"https://avatars.githubusercontent.com/u/19272022?v=3","gravatar_id":"","url":"https://api.github.com/users/ElegantSudo","html_url":"https://github.com/ElegantSudo","followers_url":"https://api.github.com/users/ElegantSudo/followers","following_url":"https://api.github.com/users/ElegantSudo/following{/other_user}","gists_url":"https://api.github.com/users/ElegantSudo/gists{/gist_id}","starred_url":"https://api.github.com/users/ElegantSudo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ElegantSudo/subscriptions","organizations_url":"https://api.github.com/users/ElegantSudo/orgs","repos_url":"https://api.github.com/users/ElegantSudo/repos","events_url":"https://api.github.com/users/ElegantSudo/events{/privacy}","received_events_url":"https://api.github.com/users/ElegantSudo/received_events","type":"User","site_admin":false},"created_at":"2016-08-06T17:28:25Z","updated_at":"2016-08-06T17:28:25Z","body":"@smeijer that's interesting, but that article doesn't even touch on the way that react-komposer is using it.\r\n\r\nReact composer is having you define a completely separate function to handle errors, as opposed to what the article outlines as you passing in one function and having an argument `error` hold the information of an error if their is one.\r\n\r\nYou're comparing apples to oranges."}}
{"actor":{"display_login":"ElegantSudo"}}