{"action":"created","issue":{"url":"https://api.github.com/repos/yahoo/react-intl/issues/109","labels_url":"https://api.github.com/repos/yahoo/react-intl/issues/109/labels{/name}","comments_url":"https://api.github.com/repos/yahoo/react-intl/issues/109/comments","events_url":"https://api.github.com/repos/yahoo/react-intl/issues/109/events","html_url":"https://github.com/yahoo/react-intl/issues/109","id":72224960,"number":109,"title":"Maybe capture error & warn instead of throw?","user":{"login":"longlho","id":198255,"avatar_url":"https://avatars.githubusercontent.com/u/198255?v=3","gravatar_id":"","url":"https://api.github.com/users/longlho","html_url":"https://github.com/longlho","followers_url":"https://api.github.com/users/longlho/followers","following_url":"https://api.github.com/users/longlho/following{/other_user}","gists_url":"https://api.github.com/users/longlho/gists{/gist_id}","starred_url":"https://api.github.com/users/longlho/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/longlho/subscriptions","organizations_url":"https://api.github.com/users/longlho/orgs","repos_url":"https://api.github.com/users/longlho/repos","events_url":"https://api.github.com/users/longlho/events{/privacy}","received_events_url":"https://api.github.com/users/longlho/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-04-30T17:20:05Z","updated_at":"2015-05-06T06:26:06Z","closed_at":null,"body":"Hi @ericf ,\r\n\r\nQuick question/suggestion: on this [line](https://github.com/yahoo/react-intl/blob/master/src/mixin.js#L26) react-intl actually `throw`s error for invalid input. Is this by design? If yes any chance we can be a bit more forgiving and `warn` instead of `throw`? The reason is that this gets bubbled up and croak the server/create unexpected behavior on client and with the React stack trace bloat it's incredibly difficult to trace it.\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/yahoo/react-intl/issues/comments/99341770","html_url":"https://github.com/yahoo/react-intl/issues/109#issuecomment-99341770","issue_url":"https://api.github.com/repos/yahoo/react-intl/issues/109","id":99341770,"user":{"login":"ericf","id":29096,"avatar_url":"https://avatars.githubusercontent.com/u/29096?v=3","gravatar_id":"","url":"https://api.github.com/users/ericf","html_url":"https://github.com/ericf","followers_url":"https://api.github.com/users/ericf/followers","following_url":"https://api.github.com/users/ericf/following{/other_user}","gists_url":"https://api.github.com/users/ericf/gists{/gist_id}","starred_url":"https://api.github.com/users/ericf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ericf/subscriptions","organizations_url":"https://api.github.com/users/ericf/orgs","repos_url":"https://api.github.com/users/ericf/repos","events_url":"https://api.github.com/users/ericf/events{/privacy}","received_events_url":"https://api.github.com/users/ericf/received_events","type":"User","site_admin":false},"created_at":"2015-05-06T06:26:06Z","updated_at":"2015-05-06T06:26:06Z","body":"What are the actual real-world use cases where you're seeing `<FormattedDate>` throw? Also, how do you deal with these sorts of exceptions for other data that you try to render in your React components that might be `null` or something?"}}