rockerest’s avatarrockerest’s Twitter Archive—№ 9,968

  1. …in reply to @dan_abramov
    dan_abramov My first approach would be catching at the point of origin (ie, not at component boundary, at impl code that might throw) and handling there
    On twitter.com Twitter logo rockerest’s avatar 2017 Jul 17 Mood 0
    1. …in reply to @rockerest
      dan_abramov "leaves tree in a broken state" => Doesn't this imply that throw-possible code is un-encapsulated at its source?
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2017 Jul 17 Mood -1 🙁