{"action":"created","issue":{"url":"https://api.github.com/repos/rorysaur/quack/issues/61","labels_url":"https://api.github.com/repos/rorysaur/quack/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/rorysaur/quack/issues/61/comments","events_url":"https://api.github.com/repos/rorysaur/quack/issues/61/events","html_url":"https://github.com/rorysaur/quack/issues/61","id":66271922,"number":61,"title":"Fix duplicate key issue","user":{"login":"jacknoble","id":1051472,"avatar_url":"https://avatars.githubusercontent.com/u/1051472?v=3","gravatar_id":"","url":"https://api.github.com/users/jacknoble","html_url":"https://github.com/jacknoble","followers_url":"https://api.github.com/users/jacknoble/followers","following_url":"https://api.github.com/users/jacknoble/following{/other_user}","gists_url":"https://api.github.com/users/jacknoble/gists{/gist_id}","starred_url":"https://api.github.com/users/jacknoble/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jacknoble/subscriptions","organizations_url":"https://api.github.com/users/jacknoble/orgs","repos_url":"https://api.github.com/users/jacknoble/repos","events_url":"https://api.github.com/users/jacknoble/events{/privacy}","received_events_url":"https://api.github.com/users/jacknoble/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-04T04:03:52Z","updated_at":"2015-04-04T04:52:40Z","closed_at":null,"body":"`Warning: flattenChildren(...): Encountered two children with the same key. Child keys must be unique; when two children share a key, only the first child will be used.` See Satish's explanation here https://github.com/rorysaur/quack/issues/21 .\r\n\r\nThis is already like the third time we've had to make our code more complicated to accommodate Firebase's weird events. How are people feeling about continuing with it? I don't think it would take that much more work to roll our own backend. We need a document store with a WebSocket connection and an event listener. I still have a slight preference for Elixir or Clojure, but I'd be fine doing it in JS if people are more comfortable with that and don't want to be distracted from learning React. "},"comment":{"url":"https://api.github.com/repos/rorysaur/quack/issues/comments/89503739","html_url":"https://github.com/rorysaur/quack/issues/61#issuecomment-89503739","issue_url":"https://api.github.com/repos/rorysaur/quack/issues/61","id":89503739,"user":{"login":"satishkunisi","id":1928378,"avatar_url":"https://avatars.githubusercontent.com/u/1928378?v=3","gravatar_id":"","url":"https://api.github.com/users/satishkunisi","html_url":"https://github.com/satishkunisi","followers_url":"https://api.github.com/users/satishkunisi/followers","following_url":"https://api.github.com/users/satishkunisi/following{/other_user}","gists_url":"https://api.github.com/users/satishkunisi/gists{/gist_id}","starred_url":"https://api.github.com/users/satishkunisi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/satishkunisi/subscriptions","organizations_url":"https://api.github.com/users/satishkunisi/orgs","repos_url":"https://api.github.com/users/satishkunisi/repos","events_url":"https://api.github.com/users/satishkunisi/events{/privacy}","received_events_url":"https://api.github.com/users/satishkunisi/received_events","type":"User","site_admin":false},"created_at":"2015-04-04T04:52:40Z","updated_at":"2015-04-04T04:52:40Z","body":"I'm open to another backend.\r\n\r\nJust to talk this particular problem through, is there a way to handle the Firebase events in the stores vs. in the components? Then components would just get their state from the stores. One idea would be to fire an event on channel's being joined / left that would propagate through to the stores and toggle the relevant Firebase listeners. "}}