{"action":"created","issue":{"url":"https://api.github.com/repos/grommet/grommet/issues/460","repository_url":"https://api.github.com/repos/grommet/grommet","labels_url":"https://api.github.com/repos/grommet/grommet/issues/460/labels{/name}","comments_url":"https://api.github.com/repos/grommet/grommet/issues/460/comments","events_url":"https://api.github.com/repos/grommet/grommet/issues/460/events","html_url":"https://github.com/grommet/grommet/issues/460","id":142744324,"number":460,"title":"Responsive Split causes re-render  & re-fetch of data","user":{"login":"linde12","id":3235069,"avatar_url":"https://avatars.githubusercontent.com/u/3235069?v=3","gravatar_id":"","url":"https://api.github.com/users/linde12","html_url":"https://github.com/linde12","followers_url":"https://api.github.com/users/linde12/followers","following_url":"https://api.github.com/users/linde12/following{/other_user}","gists_url":"https://api.github.com/users/linde12/gists{/gist_id}","starred_url":"https://api.github.com/users/linde12/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/linde12/subscriptions","organizations_url":"https://api.github.com/users/linde12/orgs","repos_url":"https://api.github.com/users/linde12/repos","events_url":"https://api.github.com/users/linde12/events{/privacy}","received_events_url":"https://api.github.com/users/linde12/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-03-22T18:52:07Z","updated_at":"2016-03-22T22:12:26Z","closed_at":null,"body":"Hello!\r\n\r\nI've encountered a problem using `Split`.\r\n\r\nWrapping a component, `<C1 />`, inside a `<Split onResponsive={this._onResponsive.bind(this);}></Split>` causes `C1` to unmount and then remount(causing me to fetch data two times in `componentWillMount`) since `_onResponsive` updates the responsive-state & if the menu should be shown or not.\r\n\r\nDo you have any solution on how to do this without re-fetching data? I want the responsive menu, but i'd like to avoid fetching more data.\r\n\r\nI think this is more of a general React-problem rather than Grommet but i'm wondering if anyone has encountered the issue and how you solved it? I'm thinking of fetching data when a react-router route is changed, but that's not optimal IMO.\r\n\r\nI followed [the docs-example](https://github.com/grommet/grommet-docs/blob/master/src/DocsSplit.js) but the DocsSplit doesn't fetch data so it'll only cause a re-render. "},"comment":{"url":"https://api.github.com/repos/grommet/grommet/issues/comments/200054189","html_url":"https://github.com/grommet/grommet/issues/460#issuecomment-200054189","issue_url":"https://api.github.com/repos/grommet/grommet/issues/460","id":200054189,"user":{"login":"eabay","id":158772,"avatar_url":"https://avatars.githubusercontent.com/u/158772?v=3","gravatar_id":"","url":"https://api.github.com/users/eabay","html_url":"https://github.com/eabay","followers_url":"https://api.github.com/users/eabay/followers","following_url":"https://api.github.com/users/eabay/following{/other_user}","gists_url":"https://api.github.com/users/eabay/gists{/gist_id}","starred_url":"https://api.github.com/users/eabay/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eabay/subscriptions","organizations_url":"https://api.github.com/users/eabay/orgs","repos_url":"https://api.github.com/users/eabay/repos","events_url":"https://api.github.com/users/eabay/events{/privacy}","received_events_url":"https://api.github.com/users/eabay/received_events","type":"User","site_admin":false},"created_at":"2016-03-22T22:12:26Z","updated_at":"2016-03-22T22:12:26Z","body":"It's OK if you store data in a redux state, data will be kept between mount/unmount cycle. But it wasn't desirable in our case to sync temporary data in a central store just to prevent this to happen. We preferred to use Layer and give the control to the user to lose filled data by closing it rather than losing it by chance just because of a resize.\r\n\r\nAnyway, I just wanted to point it out while speaking the issue."}}