{"action":"created","issue":{"url":"https://api.github.com/repos/airbnb/react-dates/issues/385","repository_url":"https://api.github.com/repos/airbnb/react-dates","labels_url":"https://api.github.com/repos/airbnb/react-dates/issues/385/labels{/name}","comments_url":"https://api.github.com/repos/airbnb/react-dates/issues/385/comments","events_url":"https://api.github.com/repos/airbnb/react-dates/issues/385/events","html_url":"https://github.com/airbnb/react-dates/issues/385","id":215430836,"number":385,"title":"A question of minimal setup for DateRangePicker","user":{"login":"Reaverart","id":1614962,"avatar_url":"https://avatars0.githubusercontent.com/u/1614962?v=3","gravatar_id":"","url":"https://api.github.com/users/Reaverart","html_url":"https://github.com/Reaverart","followers_url":"https://api.github.com/users/Reaverart/followers","following_url":"https://api.github.com/users/Reaverart/following{/other_user}","gists_url":"https://api.github.com/users/Reaverart/gists{/gist_id}","starred_url":"https://api.github.com/users/Reaverart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Reaverart/subscriptions","organizations_url":"https://api.github.com/users/Reaverart/orgs","repos_url":"https://api.github.com/users/Reaverart/repos","events_url":"https://api.github.com/users/Reaverart/events{/privacy}","received_events_url":"https://api.github.com/users/Reaverart/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-03-20T14:06:45Z","updated_at":"2017-03-22T17:19:15Z","closed_at":"2017-03-20T23:56:40Z","body":"Hey folks, thanks for awesome plugin, but I cant find a minimal setup for `DateRangePicker` in readme and all samples from storybook feels not correct because all of them uses your custom wrapper from examples folder, which not in export and its actually quite big to quickly understand how it works. \r\nSo, the thing I'm looking for is minimal setup for `DateRangePicker`, peace. Btw am I right that I have to handle manually `focusedInput` prop?"},"comment":{"url":"https://api.github.com/repos/airbnb/react-dates/issues/comments/288473312","html_url":"https://github.com/airbnb/react-dates/issues/385#issuecomment-288473312","issue_url":"https://api.github.com/repos/airbnb/react-dates/issues/385","id":288473312,"user":{"login":"majapw","id":1383861,"avatar_url":"https://avatars2.githubusercontent.com/u/1383861?v=3","gravatar_id":"","url":"https://api.github.com/users/majapw","html_url":"https://github.com/majapw","followers_url":"https://api.github.com/users/majapw/followers","following_url":"https://api.github.com/users/majapw/following{/other_user}","gists_url":"https://api.github.com/users/majapw/gists{/gist_id}","starred_url":"https://api.github.com/users/majapw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/majapw/subscriptions","organizations_url":"https://api.github.com/users/majapw/orgs","repos_url":"https://api.github.com/users/majapw/repos","events_url":"https://api.github.com/users/majapw/events{/privacy}","received_events_url":"https://api.github.com/users/majapw/received_events","type":"User","site_admin":false},"created_at":"2017-03-22T17:19:15Z","updated_at":"2017-03-22T17:19:15Z","body":"Hi @Reaverart, that makes sense. This is at least part of the reason that I will be renaming `focusedInput` to `selectedInput`, because it's not traditional DOM focus that is being handled so much as which of the two dates are you selecting at the time. Focus may actually move to different elements (and def will after the a11y PR), but we still want to know which of the start date or end date we are selecting.\r\n\r\nAs for the reason there's no default HOC, it's largely due to the reason that fully controlled components with props and callbacks is kind of the React way to do things. When I first built this, we actually did originally have a component that tracked dates and focus in its internal state, but found that most of the time these were things that the parent needed to know about and specifically, not having access to those values led to gross React antipatterns like reaching into the DOM of the child components. "}}
{"actor":{"display_login":"majapw"}}